HTTP Request
Authentication
Include your bearer token on every request:Request Body
The legal name of the account holder exactly as it appears on the bank account. This is used for payment processing and account validation.
A human-readable display name for this account (e.g.
"Primary Operating Account"). This is for your own reference and is returned in all subsequent responses.The full bank account number. This value is write-only — it is never returned in any API response after creation.
The 9-digit ABA routing number for the account. This value is write-only — it is never returned in any API response after creation.
The type of bank account. Must be one of
checking or savings.Response Fields
A successful request returns HTTP201 Created with the new bank account object.
Unique identifier for the bank account.
The initial status of a newly created account is
pending_verification, indicating that micro-deposits have been initiated.The bank account type you submitted:
checking or savings.Always
manual for accounts created via the API.The display name you provided.
The name of the financial institution, if resolved from the routing number.
The last four digits of the account number you submitted.
The last four digits of the routing number you submitted.
Whether this account has been set as the default for your business.
The timestamp at which micro-deposits were initiated. Populated immediately on successful account creation.
The timestamp at which micro-deposits landed in the account. This will be
null until the deposits arrive (typically 1–3 business days).The number of failed verification attempts. Always
0 on a newly created account.Example Request
Example Response
Micro-deposits are initiated automatically upon account creation. Check
microDepositsCompletedAt on the account — once it is non-null, the deposits have landed and you can call the verify micro-deposits endpoint to complete verification.