Create bank account (API)
Programmatically creates a new bank account for a customer using API-key authentication — no presigned URL required. The 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.
Sandbox: submit XEXX010101000 (personal) or XEX010101000 (business) as the rfc
to skip SPEI provider registration and have the account marked compliant: true
immediately. The hosted onboarding UI uses these RFCs automatically — programmatic
callers must opt in by passing them. Any other RFC in sandbox is sent to the SPEI
provider’s sandbox as a real registration and will not auto-approve. Both values are
rejected in production.
Authorizations
API key sent in the Authorization header.
Path Parameters
The customer (child org) ID. Must belong to the caller's organization or a direct child.
Body
Response
The created bank account
Abbreviated CLABE number for the bank account.
Unique identifier for the bank account. Must be a valid UUID v4.
Whether the bank account is compliant. This is a derived value — true if the
account has been explicitly marked compliant OR the owning organization is
approved (KYB'd).
Timestamp when the bank account was created.
Settlement currency (ISO 4217, e.g. MXN).
ID of the customer who owns this bank account.
Whether the bank account still needs work (e.g. failed verification) before it can be used for transactions.
Current status of the bank account.
Timestamp when the bank account was last updated.
Timestamp when the bank account was deleted (if applicable).
Etherfuse deposit CLABE number.
Custom label for the bank account.