Two-factor authentication
Whenenforce_two_factor_auth is enabled, users must verify their email address before they can link a bank account via Stripe. We send a verification code to the user’s registered email, and they enter it to continue.
You can set two-factor authentication for your organisation as a whole. When you leave enforce_two_factor_auth out of the request, the organisation setting applies. When you send true or false, that value overrides the organisation setting for that URL. To change your organisation setting, reach out to your Axle representative.
Supported verification methods: email only. See User email for how to supply it.
Custom email sender
We send payment emails, such as two-factor authentication codes and payment failure notices, from an Axle address by default. We can send them from an address on your domain or a subdomain instead.- We give you two DNS records: a DKIM TXT record and a return-path CNAME record.
- Whoever manages your DNS adds them.
- We verify the records and send a test email.
- Once the test email arrives, we switch your payment emails to the new address.
Optional portal behaviour
Hide transactions
Sethide_transactions to true to hide the transaction history in the portal. This helps when:
- You want a one-off payment flow: users withdraw and return, without browsing their full history.
- You already show transaction history in your app: users don’t see the same information twice.
Skip straight to bank account setup
Whenauto_redirect_to_setup is true:
- If the user has no bank account linked, they skip the balance page and go straight into bank account setup.
- If the user already has a bank account, they see the normal balance page.

