How it works

  1. You send one payout request (TypeCredit=37) with the beneficiary's bank details. The answer is Reply=553 (payout received). There is no redirect: D3Redirect is not returned for a bank payout.
  2. We create the payment from your balance in the request currency and send it to the bank payout partner configured for your account and the beneficiary's country. The transaction moves to 001 (payout in progress). If your balance does not cover the amount, or the request breaks a limit, the transaction is declined instead (for example 715 - insufficient funds).
  3. When the payout is completed the transaction moves to 000; if the bank or the partner rejects it, it is declined with the reason. Both are sent to your notification_url (or the notification URL set on your account).

Keep the TransID from the first answer: the final notification carries it as pending_trans_id (its trans_id is the final transaction), and you can check the status at any time with the Status Check.

Send every field your corridor lists below. The partner that pays a corridor can change, and each partner validates its own set of beneficiary details. A request that carries the full set is accepted by all of them; a missing detail can be rejected by the partner after the payout was accepted (reply 751).

Request Fields

Field Description MaxLength Required
CompanyNumYour company number - #######7Yes
TransType0 = sale1Yes
TypeCredit37 = payout2Yes
Payments12Yes
AmountAmount to pay out, e.g. 150.0010Yes
CurrencyCurrency ID - list. AUD = 4, NZD = 19, EUR = 2. The payout is taken from your balance in this currency.3Yes
CPMPayout method ID set up for your account - 149 (Online Bank Transfer) unless support gave you another one5Yes
OrderYour unique reference for the payout100Recommended
MemberBeneficiary (account holder) full name, e.g. Jane Citizen200Yes
PayoutAccountIBAN (EU) or account number (AU, NZ). Spaces and dashes are removed.50Yes 1
CP3SWIFT / BIC of the beneficiary's bank11EU
CP7Bank name100Recommended
CP8Bank country, ISO 2 letters (AU, NZ, DE...). Default: BillingCountry, then the IBAN country.2Yes
CP9BSB, 6 digits (Australia). For New Zealand you may send bank + branch here and the rest of the account in PayoutAccount.6AU
CP10Payout purpose code, e.g. SUPA (supplier payment). Ask support for the codes enabled on your account.20Yes 2
CP11Payout scheme of the corridor - see the corridor tables below (e.g. au_bank_acct, nz_bank_directcredit_nzd)50NZ, EU 2
CP12Beneficiary type: I = individual (default), B = business1Yes
CP13 / CP14Beneficiary first name / last name. Default: Member split at the first space.100Individual
CP15Company name. Default: Member.200Business
CP16 / CP17PayID and PayID type (EMAIL, MOBILE, ABN) - Australia, instead of BSB + account number100 / 20AU PayID
DateOfBirthBeneficiary date of birth, yyyyMMdd8Individual
PersonalNumBeneficiary national ID / document number (business: company number)50Recommended
EmailBeneficiary e-mail100Yes
PhoneNumberBeneficiary phone with country code, e.g. +6140000000030Recommended
BillingAddress1Beneficiary street address200Yes
BillingCityBeneficiary city100Yes
BillingStateBeneficiary state / region (AU: NSW, VIC...)50Recommended
BillingZipCodeBeneficiary postal code20Yes
BillingCountryBeneficiary country, ISO 2 letters2Yes
notification_urlURL that receives the final status of the payout (Notification V2). It can also be set on your account.255Recommended
ClientIPIP address of the request15Recommended
CommentFree text500Optional
Signature Base64 of SHA256 over CompanyNum + TransType + TypeCredit + Amount + Currency + PersonalHashKey, URL encoded. Use the values exactly as you send them. See Signature. 50 Yes 3

1 In Australia a PayID (CP16 + CP17) can replace PayoutAccount + CP9.
2 Required unless support has set a default purpose / scheme for your account.
3 When signature verification is enabled on your account.

Code example

Code Example
var Signature = CryptoJS.SHA256(CompanyNum + 0 + 37 + Amount + Currency + PersonalHashKey);
var hash = encodeURIComponent(Signature.toString(CryptoJS.enc.Base64));

// POST application/x-www-form-urlencoded
var body = "CompanyNum=" + CompanyNum + "&TransType=0&TypeCredit=37&Payments=1"
    + "&Amount=" + Amount + "&Currency=" + Currency + "&CPM=149"
    + "&Order=" + encodeURIComponent(Order)
    + "&Member=" + encodeURIComponent(Member)
    + "&PayoutAccount=" + encodeURIComponent(PayoutAccount)
    + "&CP8=" + BankCountry + "&CP10=" + Purpose + "&CP11=" + Scheme
    + "&CP12=I&CP13=" + encodeURIComponent(FirstName) + "&CP14=" + encodeURIComponent(LastName)
    + "&DateOfBirth=" + DateOfBirth + "&Email=" + encodeURIComponent(Email)
    + "&BillingAddress1=" + encodeURIComponent(Address) + "&BillingCity=" + encodeURIComponent(City)
    + "&BillingZipCode=" + ZipCode + "&BillingCountry=" + Country
    + "&notification_url=" + encodeURIComponent(notification_url)
    + "&Signature=" + hash;

post("https://process.coriunder.cloud/member/remote_charge.asp", body);

Response example

Response
TransType=0&
Reply=553&
TransID=24674&
Date=07/11/2026 11:58:29&
Order=PO-AUD-0001&
Amount=150.00&
Payments=1&
Currency=4&
ReplyDesc=Payout in progress&
Source=SILENTPOST&
debit_refnum=&
signType=SHA256&
signature=...

Error response example

Missing or invalid beneficiary details are declined at once with Reply=007. ReplyDesc lists every missing field, so you can fix them all in one go and send a new request with a new Order.

Response
TransType=0&
Reply=007&
TransID=24675&
Date=07/11/2026 12:04:51&
Order=PO-AUD-0002&
Amount=150.00&
Payments=1&
Currency=4&
ReplyDesc=Missing or invalid beneficiary details: the first and last name (CP13 / CP14, or Member with a space), the IBAN or account number (PayoutAccount) or a PayID (CP16)&
Source=SILENTPOST&
debit_refnum=&
signType=SHA256&
signature=...

Corridors

Australia (AUD) New Zealand (NZD) Europe (EUR, SEPA)
Currency / CP8 4 / AU 19 / NZ 2 / the bank's country (DE, FR, ES...)
Account Bank account: CP9 = BSB (6 digits), PayoutAccount = account number (4 to 10 digits)
or PayID: CP16 = PayID, CP17 = EMAIL / MOBILE / ABN 		PayoutAccount = the full account number, 15 or 16 digits: bank (2) + branch (4) + account (7) + suffix (2 or 3), e.g. 1234560123456000 PayoutAccount = IBAN, CP3 = BIC (required)
CP11 scheme au_bank_acct (BSB + account), au_bank_payid (PayID). Optional: it is derived from the account details when not sent. nz_bank_directcredit_nzd (required unless set on your account) The SEPA scheme code given by support (required unless set on your account)
Beneficiary Individual (CP12=I): Member, CP13 first name, CP14 last name, DateOfBirth, Email, PhoneNumber, PersonalNum.
Business (CP12=B): Member, CP15 company name, PersonalNum (company number), Email, PhoneNumber; CP13 / CP14 = contact person when you have one.
Address BillingAddress1, BillingCity, BillingZipCode, BillingCountry - required in all corridors; BillingState recommended (required by some partners in Australia).
Purpose CP10 purpose code, e.g. SUPA (supplier), SALA (salary), SELF (own account) - the codes enabled on your account are given by support.

Australia - BSB

Request
CompanyNum=3411419&
TransType=0&
TypeCredit=37&
Payments=1&
Amount=150.00&
Currency=4&
CPM=149&
Order=PO-AUD-0001&
Member=Jane Citizen&
PayoutAccount=123456789&
CP9=062000&
CP8=AU&
CP10=SUPA&
CP11=au_bank_acct&
CP12=I&
CP13=Jane&
CP14=Citizen&
DateOfBirth=19850214&
Email=jane@example.com&
PhoneNumber=+61400000000&
BillingAddress1=1 George Street&
BillingCity=Sydney&
BillingState=NSW&
BillingZipCode=2000&
BillingCountry=AU&
notification_url=https://merchant.example.com/payouts&
Signature=...

New Zealand

Request
CompanyNum=3411419&
TransType=0&
TypeCredit=37&
Payments=1&
Amount=200.00&
Currency=19&
CPM=149&
Order=PO-NZD-0001&
Member=Kiwi Supplies Ltd&
PayoutAccount=1234560123456000&
CP8=NZ&
CP10=SUPA&
CP11=nz_bank_directcredit_nzd&
CP12=B&
CP15=Kiwi Supplies Ltd&
PersonalNum=9429041234567&
Email=accounts@kiwisupplies.example&
PhoneNumber=+64210000000&
BillingAddress1=1 Queen Street&
BillingCity=Auckland&
BillingZipCode=1010&
BillingCountry=NZ&
notification_url=https://merchant.example.com/payouts&
Signature=...

Europe - SEPA

Request
CompanyNum=3411419&
TransType=0&
TypeCredit=37&
Payments=1&
Amount=500.00&
Currency=2&
CPM=149&
Order=PO-EUR-0001&
Member=Max Mustermann&
PayoutAccount=DE89370400440532013000&
CP3=COBADEFFXXX&
CP8=DE&
CP10=SUPA&
CP11=<SEPA scheme from support>&
CP12=I&
CP13=Max&
CP14=Mustermann&
DateOfBirth=19800101&
Email=max@example.com&
BillingAddress1=Hauptstrasse 1&
BillingCity=Berlin&
BillingZipCode=10115&
BillingCountry=DE&
notification_url=https://merchant.example.com/payouts&
Signature=...

Reply codes

CodeMeaningWhen
553Payout receivedAnswer to the request
001Payout in progress - the payment was created from your balanceStatus check (no notification for this step)
000Payout completedNotification
007Missing or invalid beneficiary details - the description lists themAnswer to the request
508Not a payout request (TypeCredit 37, TransType 0)Answer to the request
715Insufficient funds in your balanceNotification
702 / 704 / 706Single / daily / monthly payout limitNotification
708 / 710 / 714Payout country or payouts not allowed for your accountNotification
716Payout canceledNotification
719Technical error - you may send a new request with a new OrderEither
720 / 741Rejected by risk checks / payouts restrictedNotification
750The payout failed at the bank or partnerNotification
751The beneficiary details were rejected - check the account and the fields of your corridorNotification
752The payout could not be created (for example no payout route for this country / currency)Notification
753The beneficiary details could not be savedNotification

Notification

The final status is posted to your notification_url (form body, Notification V2):

reply_code000 or the decline code
reply_descDescription
trans_idThe final (approved or declined) transaction
pending_trans_idThe TransID you received with 553
trans_datedd/MM/yyyy HH:mm:ss
trans_amount / trans_currencyThe payout amount and currency (ISO)
trans_orderYour Order
merchant_idYour CompanyNum
client_fullname / client_phone / client_emailThe beneficiary
signaturebase64(sha256(trans_id + trans_order + reply_code + trans_amount + trans_currency + PersonalHashKey))

Notification example - completed

The payout was paid to the beneficiary. trans_id is the approved transaction; pending_trans_id is the TransID you received with 553.

Notification (POST body)
reply_code=000&
reply_desc=Payout completed, wire 51234&
trans_id=1082231&
trans_date=07/11/2026 14:21:07&
otrans_amount=150.00&
trans_amount=150.00&
otrans_currency=AUD&
trans_currency=AUD&
trans_order=PO-AUD-0001&
merchant_id=3411419&
client_fullname=Jane Citizen&
client_phone=+61400000000&
client_email=jane@example.com&
payment_details=Online Bank Transfer&
trans_type=0&
pending_trans_id=24674&
signature=...

Notification example - declined

Your balance did not cover the payout, so no payment was created (715). Any other decline code from the table above arrives the same way.

Notification (POST body)
reply_code=715&
reply_desc=Insufficient funds&
trans_id=24690&
trans_date=07/11/2026 12:20:15&
otrans_amount=200.00&
trans_amount=200.00&
otrans_currency=NZD&
trans_currency=NZD&
trans_order=PO-NZD-0001&
merchant_id=3411419&
client_fullname=Kiwi Supplies Ltd&
client_phone=+64210000000&
client_email=accounts@kiwisupplies.example&
payment_details=Online Bank Transfer&
trans_type=0&
pending_trans_id=24680&
signature=...

The body is form-encoded (shown decoded, one field per line). Check the signature before you act on a notification, and answer HTTP 200. To verify a 000 signature: base64(sha256("1082231" + "PO-AUD-0001" + "000" + "150.00" + "AUD" + PersonalHashKey)).

APM Payout

Payouts to local payment methods (PIX, SPEI...).
Status Check

Check the status of a specific transaction.
Signature

How to sign a request.