Programmatically creates a new bank account for a customer using API key authentication. No presigned URL is required. The account registration data (name, CURP, RFC, CLABE, etc.) is validated and sent to the payment processor. Bank accounts require verification before they can be used for transactions.
API key for authentication. Pass the key directly (e.g., Authorization: your-api-key). Do not use a Bearer prefix.
ID of the customer to create the bank account for
Bank account registration data. Accepts either Personal or Business format. The variant is auto-detected based on the fields present (untagged union).
{
"transactionId": "123e4567-e89b-12d3-a456-426614174000",
"firstName": "Juan",
"paternalLastName": "García",
"maternalLastName": "López",
"birthDate": "19900101",
"birthCountryIsoCode": "MX",
"curp": "GALJ900101HDFRRN09",
"rfc": "GALJ9001016V3",
"clabe": "012345678901234567"
}If true, skips automatic approval in sandbox/devnet environments
Optional label for the bank account
Optional UUID for the bank account. Auto-generated if omitted.
Bank account created successfully
Unique identifier for the bank account. Must be a valid UUID v4.
ID of the customer who owns this bank account
Timestamp when the bank account was created
Timestamp when the bank account was last updated
Timestamp when the bank account was deleted (if applicable)
Abbreviated CLABE number for the bank account
Etherfuse deposit CLABE number
Custom label for the bank account
Whether the bank account is compliant. This is a derived value — true if the account has been explicitly marked compliant OR if the owning organization is approved (KYB'd).
Current status of the bank account
pending, awaitingDepositVerification, active, inactive