Create a transaction

Create a new transaction with the provided details.

Payout rails are verification-gated: when the client's verification program gates PAYOUT, the source wallet's holder must be verification-cleared — an unverified, restricted or suspended holder is declined with 400 (reason VERIFICATION_RESTRICTED / VERIFICATION_SUSPENDED or a blocked-pending-verification message), and a clearance outage returns a retriable 503 for enrolled clients (see the 503 response).

Direct debit (AUD_DD_1, in development). Available in sandbox for integration testing, not yet in production. Pulls funds from a payer's Australian bank account into your wallet through the BECS direct debit scheme. The transaction is recorded with type RECEIVE. You must hold the payer's Direct Debit Request authority and create a mandate first (POST /customers/v1/transaction-mandates).

from: your AUD wallet that receives the funds. As for the other _1 AUD rails it must be an ACTIVE KOBBLE_AUD_1 or KOBBLE_AUD_2 wallet, otherwise 400 Invalid wallet id or state.

to: an ACTIVE beneficiary holding the payer's bank account (bank_code_type BSB, bank_country AUS). A mandate is not tied to a bank account, so always debit the payer the mandate was created for.

mandate_id: REQUIRED.

amount: at most the mandate's max_amount.

reference: the first 18 characters appear on the payer's bank statement.

Status lifecycle: PENDING once submitted to the direct debit scheme; ACCEPTED when the debit clears; DECLINED, with a reason, when the submission is rejected. Clearance is reported once per business day, so expect ACCEPTED to take business days, not seconds. Outcomes are signalled by the transaction-accept / transaction-decline webhooks.

Mandate rules checked at creation, each failing with HTTP 400 and this exact message:

Mandate id is required: mandate_id was omitted.

Invalid mandate id: the mandate does not exist or belongs to another client.

Mandate is not active: the mandate is INACTIVE.

Maximum mandate iterations exceeded: last_iteration has reached max_iterations.

Mandate has expired: expires_at is not after today (UTC).

Mandate asset mismatch: the from wallet is not an AUD wallet.

Amount exceeds mandate max amount: amount is greater than max_amount.

There is an ongoing transaction for the mandate: the previous debit is still PENDING. Only one debit can be in flight per mandate.

Mandate transaction already exists for today: a debit was already created on the mandate today (UTC). One debit per mandate per calendar day.

Mandate next transaction date is not due yet: the schedule below does not allow a debit yet.

Schedule: for NON_RECURRING the debit is due from starts_at. For recurring frequencies the next debit is due one period after the previous debit's date, and the FIRST debit one period after starts_at (a MONTHLY mandate starting 1 March allows its first debit from 1 April). Set starts_at one period before the first collection date.

See the Direct debit guide for the end-to-end flow.

application/json

Transaction created. Payouts (every payment_type other than INTER_WALLET) are created PENDING and resolve asynchronously - subscribe to transaction-accept/transaction-decline webhooks.

Bodyapplication/json

Example

{
    "id": "9b1f05d8-f08f-4974-ae2b-df1e475e5024",
    "amount": 1,
    "asset": "AUD",
    "asset_class": "CURRENCY",
    "created_at": "2025-01-14T16:42:56.086Z",
    "external_id": "111",
    "from": "3d83ed2b-b760-4101-adf2-4f83ed57d366",
    "payment_type": "MANUAL_CREDIT",
    "reference": "in dolore nostrud sit velit",
    "status": "DECLINED",
    "to": "4e624f4c-d49c-4cb4-bda3-1c734042d134",
    "type": "RESERVATION",
    "updated_at": "2025-01-14T16:42:56.088Z",
    "metadata": {},
    "info": null,
    "program_id": null,
    "owner": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "mandate_id": null
}

Create a transaction

Request

Request Code Samples

Responses