Skip to main content
POST
Create an AUD payout

What this endpoint does

Creates an AUD payout to a saved beneficiary and durably reserves its source debit from this tenant account’s AUD wallet.

When to use it

Submit it after choosing the beneficiary, confirming the amount and purpose, and reviewing the effective fee and available balance.

Before you call

Use a secret API key with treasury:write. The beneficiary, its accepted evidence when required, limits, BSB/account rail, and wallet balance must all be eligible. Sumsub share tokens are submitted with beneficiary creation, not here.

Money and balance effect

On acceptance, the payout source debit is reserved so it cannot be spent twice. Settlement captures the reservation; a proven pre-settlement failure releases it, while returns follow the configured return policy.

States and completion

accepted means policy passed and funds are reserved. held needs review; submitted reached the bank rail; settled, failed, and returned describe later outcomes.

Safe retries

Send a unique Idempotency-Key for the logical action. If the response is lost, retry the same payload with the same key; never create a new key merely because the first response timed out. Read Beneficiaries and payouts for the complete workflow.

Authorizations

Authorization
string
header
required

Send the same Wayex API key as Authorization: Bearer <key>.

Headers

Idempotency-Key
string
required

A unique key for this logical action. Reuse the same key and identical payload when retrying after an unknown response.

Required string length: 8 - 255

Body

application/json
beneficiaryId
string
required
Minimum string length: 1
amount
string
required
Pattern: ^\d+(\.\d+)?$
currency
enum<string>
required
Available options:
AUD
externalReference
string
required
Minimum string length: 1
purpose
string
required
Required string length: 1 - 255
walletProviderReference
string
Minimum string length: 1
downstreamMerchantReference
string
Minimum string length: 1
evidenceId
string
Minimum string length: 1

Response

201 - application/json
id
string
required
Minimum string length: 1
clientId
string
required
Minimum string length: 1
beneficiaryId
string
required
Minimum string length: 1
amount
object
required
fee
object
required
sourceDebit
object
required
status
enum<string>
required
Available options:
accepted,
held,
submitted,
settled,
failed,
returned
configurationId
string
required
Minimum string length: 1
externalReference
string
required
Minimum string length: 1
purpose
string
required
Required string length: 1 - 255
reservation
object
required
nextAction
enum<string>
required
Available options:
none,
wait_for_settlement,
contact_support,
retry_new_request,
review_balance
createdAt
string<date-time>
required
updatedAt
string<date-time>
required
walletProviderReference
string
Minimum string length: 1
downstreamMerchantReference
string
Minimum string length: 1
evidenceId
string
Minimum string length: 1
providerReference
string
Minimum string length: 1
statusReason
string
Minimum string length: 1