For the complete documentation index, see llms.txt. Append
.mdto any page URL for its markdown version.
Partners integrating via the Banxa Native API control the full user experience, including the presentation of required legal agreements. Banxa does not surface these agreements on the partner's behalf. Failure to display required agreements before a user transacts is a compliance breach and may result in transaction failures or go-live being blocked.
Required agreements are additive — each layer below builds on the previous. Display all agreements that apply to your users' jurisdiction before they initiate their first transaction.
Every user transacting through the Banxa Native API must be shown and must accept:
In addition to the above, US users must also be shown and accept:
Users in the following states are processed through a licensed sub-processor and must also accept that sub-processor's agreements, in addition to all of the above.
Axnab does not require a separate privacy policy document at this layer.
Washington (WA) is processed through both Zerohash and Axnab. Users in WA must accept agreements from both sub-processors.
ACH is available for off-ramp only. In addition to all of the above, US users completing an ACH off-ramp must also be shown and accept:
- Agreements must be presented clearly before the user initiates their first transaction — not buried in a settings flow or footer.
- Acceptance must be captured explicitly (e.g. a checkbox with a visible link to each document).
- Banxa's compliance team will review a screen recording of the acceptance flow before approving go-live.
For ACH off-ramps, acceptance is also captured at the API level with the tosAccepted field on POST /eapi/v0/ramps.
When it is required: Banxa checks two conditions at ramp creation:
- The payout method is ACH (
ach-bank-transfer) - The user has not previously accepted the Bridge terms of service
If both are true, the request must include "tosAccepted": true. Omitting it returns a 422 validation error. The field only accepts true: sending false also returns a 422, so leave the field out when you aren't sending true.
Once Banxa has recorded the user's acceptance, the signed agreement is stored on the user's record and shared with Bridge. Later ACH off-ramps by the same user don't need tosAccepted. Sending true again is accepted.
tosAccepted goes in target.fiat, next to the bank details:
{
"identityReference": "user-abc123",
"source": {
"crypto": {
"id": "USDT",
"blockchain": "ETH",
"walletAddress": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb"
}
},
"target": {
"fiat": {
"id": "USD",
"method": "ach-bank-transfer",
"tosAccepted": true,
"instructions": {
"bankName": "Bank of America",
"accountName": "John Doe",
"accountNumber": "123456789012",
"routingNumber": "121000358"
}
}
},
"cryptoAmount": "200"
}When you create the ramp from a quote, send tosAccepted at the top level of the body instead.
{
"status": 422,
"message": "...",
"errors": {
"target.fiat.tosAccepted": ["..."]
}
}The error is keyed by the field; the message text may change. See Error Codes.
| User | Required agreements |
|---|---|
| All users | Banxa Terms & Conditions |
| US users | + Banxa Privacy Policy, Biometric Privacy Disclosure, State Disclosures |
| US users in TX, WI, VA | + Zero Hash ToS, US Licenses & Disclosures, Privacy Policy |
| US users in GA, MN | + Axnab T&Cs, Axnab Biometric Privacy Disclosure |
| US users in WA | + Zero Hash ToS, US Licenses & Disclosures, Zero Hash Privacy Policy, Axnab T&Cs, Axnab Biometric Privacy Disclosure |
| US users off-ramping via ACH | All of the above (where applicable) + Bridge Terms of Service + Bridge Privacy Policy + tosAccepted on the first ACH off-ramp |
Go-live requirement: Before going live with any US users, provide your Banxa contact with a screen recording showing where each required agreement is displayed and how acceptance is captured. For ACH specifically, production access will not be granted until this review is complete.