Headers
PartnerApiKey (string) - API key associated with the partner.Partner API Key RequiredRequires
partner-api-key
for authentication to ensure only authorized partners can access this data.See 🔑 API Key Generation Guide for getting your API keyInput Body
All fields are required unless they’re explicitly marked as optional- userId (string): The unique identifier of the user who owns this bank information.
- bankName (string, optional): The name of the bank where this account is held. This field is required if supportedBankId is not provided.
- supportedBankId (string, optional): The identifier for the bank where this account is held.
- accountNumber (string): The account number associated with this bank account.
- accountType (string): The type of the bank account.
- Possible values:
- CHECKING
- SAVINGS
- Possible values:
- clabe (string, optional): The account identifier specific to bank accounts in Mexico.
- country (string): The country where this bank account information is applicable.
- Possible values:
- MX
- DO
- Possible values:
- documentNumber (string, optional): The nationality identifier for the user. If not provided, the document number from the user’s KYC information will be used.
Example
JSON
Response
This is the response body returned after creating or retrieving a user’s bank information. All fields are required unless explicitly marked as optional. Below are the details of each field included in the response: id (string): The unique identifier for this bank information record. userId (string): The unique identifier of the user who owns this bank information. partnerId (string, optional): The unique identifier of the partner that owns this bank information. bankName (string, optional): The name of the bank if it is not listed as a supported bank. accountNumber (string): The account number associated with this bank account. accountType (enum: SupportedBankAccountType): The type of the bank account. clabe (string, optional): The CLABE number specific to Mexican banks. country (string): The country where this bank account information is applicable.
- Possible values:
- CHECKING
- SAVINGS
- Possible values:
- ON_RAMP
- OFF_RAMP
Example
JSON
Use cases
Register account for off ramp transfers A partner wants to register a new bank account details to transfer fiat currency to the user. Update bank information about the user A partner who wants to update old information about the user’s bank accountHeaders
Country code of the flow (MX or DO)
Api key for the affiliated partner that is performing the request
Body
application/json
The id of the user that owns this bank information.
Example:
"123e4567-e89b-12d3-a456-426614174000"
The identifier for this account in the specified bank.
Example:
"12345678901"
The type of account (CHECKING / SAVINGS).
Available options:
SAVINGS
, CHECKING
Example:
"SAVINGS"
Country of the bank account.
Available options:
MX
, DO
, US
, AT
, BE
, BG
, HR
, CY
, CZ
, DK
, EE
, FI
, FR
, DE
, GR
, HU
, IE
, IT
, LV
, LT
, LU
, MT
, NL
, PL
, PT
, RO
, SK
, SI
, ES
, SE
, IS
, LI
, NO
, CH
, GB
, MC
, SM
, AD
, VA
Example:
"ES"
The name of the bank this account belongs to. Required for DO.
Example:
"Banco Popular"
18–digit CLABE for Mexican accounts.
Example:
"014680260346007120"
Document number tied to this bank account (country specific).
Example:
"RNC1234567"
IBAN for SEPA / EU accounts.
Example:
"ES9121000418450200051332"