Skip to main content
POST
Create Beneficiary
This endpoint will be deprecated on September 1, 2026. Use Create Beneficiary V3 instead.

Rules

  • Beneficiary creation requires the customer to be in the APPROVED status.
  • Two beneficiaries with the same destination are not allowed.

De-Duplication Logic

For bank accounts, the system checks: bank_account.scheme, bank_account.number, bank_routing.scheme, bank_routing.number. For e-wallets: e_wallet.scheme, e_wallet.number.

Country-Specific Validation

GBR (United Kingdom)

  • Bank account number: Must match ^[0-9]{4,9}$ for both LOCAL and SWIFT schemes.

Authorizations

Authorization
string
header
required

Bearer token authentication. Obtain token from Issue a Token endpoint

Body

application/json
customer_id
string
required
Example:

"cust_123456"

country
string
required
Pattern: ^[A-Z]{3}$
Example:

"USA"

currency
string
required
Example:

"USD"

account_holder
Individual · object
required
account_holder_address
object
required
receiver_meta_data
object
required
developer_fee
object
required
deposit_instruction
object
required
refund_instruction
object
required
bank_account
object
required
bank_routing
object[]
required
bank_address
object
required
counter_party
enum<string>

Indicates whether the beneficiary is a first-party or third-party account. Optional.

Available options:
FIRST_PARTY,
THIRD_PARTY
Example:

"FIRST_PARTY"

settlement_config
object

Response

Beneficiary created successfully

data
object