Skip to main content
POST
Create a beneficiary

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Request body for registering a new fiat payout beneficiary.

idempotencyKey
string<uuid>
required

Client-generated UUID for idempotent submission.

Example:

"a1b2c3d4-e5f6-7890-abcd-ef1234567890"

customerType
enum<string>
required

Whether the beneficiary is an individual or a business.

Available options:
INDIVIDUAL,
BUSINESS
destinationCountry
string
required

ISO 3166-1 alpha-2 destination country code.

Example:

"MX"

destinationCurrency
string
required

Destination fiat currency code.

Example:

"MXN"

paymentMethod
string
required

Payment rail. Must match a supported corridor rail. Examples: SPEI, ACH-BANK-TRANSFER, SD-ACH, SEPA, WIRE, PIX.

Example:

"SPEI"

bankAccount
object
required

Bank and account fields required by the corridor. Keys are the field names returned by GET /v1/beneficiaries/requirements with type TEXT (excluding travel-rule fields). Values must satisfy any pattern constraint.

Example:
travelRule
object
required

Beneficiary travel-rule / PII fields required by the corridor. Keys are the field names returned by GET /v1/beneficiaries/requirements for travel-rule fields (prefixed BENEFICIARY_). ADDRESS type values are nested objects.

Example:
refId
string<uuid>

Optional customer-assigned reference identifier.

Example:

"d4e5f6a1-b2c3-7890-abcd-ef1234567890"

nickname
string

Optional display label for this beneficiary.

Example:

"Vendor A - MXN"

Response

Beneficiary registered. Screening is asynchronous; status is INACTIVE.

data
object

A registered fiat payout beneficiary.