Add a Payee Bank
Adds a cross-border bank account for a payee.
Identify the payee by payee_id. Send the bank details — account_number, country (ISO2),
bank_acc_type, identifier_type, identifier_value, an optional bank_nick_name and an optional
payout_bank_id. Each field only accepts values within the maximum length allowed by the payee rules
for the destination country — see GET /cross-border/payee-rules. Returns the created cross-border bank.
Headers
Unique platform identifier (UUID). You receive this during onboarding. Must be sent with every API request.
HMAC-SHA256 request signature for authentication. Use your platform secret key to compute it as: METHOD + PATH + QUERY + BODY_HASH.
Path Parameters
Unique identifier (UUID) of the platform user who owns the payee bank.
Body
Platform-side add cross-border payee bank request — stores the payee's bank details.
The payer is NOT fixed here: it is supplied at payout time, and the payer's mandatory fields are
fetched from the payer rules and validated on each payout. So this request carries only the core
bank fields plus the owning payee (payee_id).
Payee's user id.
"f47ac10b-****-****-****-0e02b2c3d479"
Nickname for the payee bank.
1 - 100"HDFC savings"
64Payee country ISO2.
80"IN"
Beneficiary bank account type. Mapped to the Uniteller bankAccType code at payout time
(savings -> AHO, current -> CTE, no_needed -> NON).
savings, current, no_needed "savings"
Bank identifier value for the country (IFSC for India, BSB for Australia, routing number for the US, etc.).
64"SBIN0000123"
Payout bank id — only enter this for Pakistan. For every other country it is optional and can be omitted.
40"921874"
Response
Successful Response
Indicates whether the request was processed successfully.
true
A short, human-readable message describing the result of the request.
"Operation completed."
The main response payload, if applicable
The Unix timestamp (in seconds) indicating when the response was generated.
1718006400

