Bank account linkage is the third step in most flows: Create User → KYC → Bank Account Linkage → Transaction.
Why a bank account gets linked
Deliver funds — Offramp
On offramp, the linked bank account is the payout destination — once a sell transaction is confirmed, fiat is sent there.
Pull funds — Onramp
On some onramp flows, the linked bank account is the funding source money is pulled from to convert into stablecoin.
Ways to link a bank account
There’s no single method used everywhere — which one applies depends on the corridor and the flow.- Through API
- Through Hosted Widget
The client collects the user’s bank details directly (account number, bank code, IBAN, sort code, etc., depending on the country) and submits them via a direct API call. This is the most common method for offramp corridors, where Saber needs a specific payout destination on file.See Bank Account — Through API for the request format and country-specific field requirements.
Not every flow has a standalone bank-linkage step. Some onramp payment methods (for example, an Open Banking redirect) collect and authorize the bank connection at the moment of payment instead of as a separate upfront step. Where that’s the case, it’s called out on that flow’s own page — see the currency-specific guides below.
Approval and validation
Once submitted, a bank account typically enters aPENDING state before becoming APPROVED. How that approval happens differs by country:
- Instant approval — the account is validated and approved immediately, with no further action needed.
- Penny-drop verification — a small verification transfer is made to the account to confirm it’s valid and belongs to the named holder before it’s approved.
Webhooks
Bank account status changes (for example, moving fromPENDING to APPROVED, or a validation failure) can be pushed to your configured webhook URL instead of requiring you to poll. See Bank Account — Webhooks for the event payloads.