Skip to content
guideNovember 11, 2026 · 9 min read

Fiat rails for a crypto exchange: bank, EMI, PSP and card on-ramp compared

Four ways to add a fiat on-ramp to a crypto exchange: bank account, virtual IBANs, PSP pay-by-bank or card partner. How each connects and what it costs.

BitPolaris Engineering

A fiat on-ramp for a crypto exchange is the connection that lets a customer move money from a bank account or card into the exchange, and back out again. There are four ways to build one: your own bank account with reconciliation, virtual IBANs from an electronic money institution (EMI) or bank, a payment service provider (PSP) with pay-by-bank or local rails, and a card on-ramp partner that sells the crypto itself. They differ in who holds the money, who carries fraud and chargeback risk, and how much reconciliation your team does every day.

This guide compares the four rails from the operator’s side: how each one connects to the exchange, what your ledger and console must do, what usually goes wrong, and what it costs. It is written for founders, CTOs and compliance heads at exchanges and brokers that have a licence or are applying for one. Which rails your licence allows, and whether you may hold client money at all, is a question for your counsel and your regulator.

The four fiat rails at a glance

Own bank account EMI or bank virtual IBANs PSP (pay-by-bank, local rails) Card on-ramp partner
Where the money lands Your account at the bank Your master account, one virtual IBAN per customer The PSP’s account, then settled to yours Never reaches you; the partner sends crypto
How a deposit is matched Payment reference typed by the customer The IBAN itself identifies the customer The PSP’s payment ID and webhook A blockchain deposit to the customer’s address
Customer’s name check Your team or rule, from the statement Usually in the provider’s data In the PSP’s data, varies by method Partner’s KYC
Chargeback risk Low (credit transfers are not charged back) Low Low for bank methods; card methods carry it With the partner
Withdrawals You initiate from the bank portal or API Provider API Payout API, where offered Off-ramp, if the partner offers it
Who does KYC You You, and the provider checks you You, and the PSP checks you The partner, for the purchase
Typical blocker The bank account itself Provider’s appetite for crypto clients Provider’s appetite and method coverage Fee level and country coverage

The first three rails credit a fiat balance in your ledger. The card on-ramp does not: the partner is the seller, the customer buys crypto from the partner, and the exchange sees a crypto deposit arriving at the customer’s address.

Rail 1: your own bank account

The simplest rail on paper. You open a client-money or operating account, publish its details in the deposit screen, and ask each customer to put a unique reference in the transfer. Your system reads the bank statement, finds the reference, checks the sender name and credits the account.

What makes it hard is the bank, not the code. Many banks will not open accounts for crypto businesses, or only after the licence is granted; in our launch calendar fiat comes a month or two after the first crypto trade for this reason. When the account exists, the daily work is reconciliation:

  • Missing or wrong references. A share of customers will type the reference wrongly or leave it out. Those payments go to an exceptions queue where an operator matches them by name and amount, or returns them.
  • Third-party payments. Most exchanges accept deposits only from an account in the customer’s own name, and pay withdrawals only to such an account. This is usually a bank or AML policy rather than a single rule in law, but it is the control banks ask about first. The statement has to carry the payer’s name for the check to work.
  • Statement timing. If you read statements once a day, deposits wait up to a day. An API or intraday statement feed from the bank shortens that; ask for it before you sign.

In the euro area, instant credit transfers are now standard for banks. Regulation (EU) 2024/886 required euro-area payment service providers to receive instant euro transfers from 9 January 2025 and send them from 9 October 2025, and to offer verification of the payee’s name from 9 October 2025 (Articles 5a(8) and 5c(9)). Payment institutions and EMIs in the euro area have until 9 April 2027. For an exchange, instant receipt means a customer’s euro deposit can arrive in seconds, which only helps if your statement feed and matching run as fast.

Rail 2: virtual IBANs from an EMI or bank

A virtual IBAN is an account number that routes into your master account but identifies one customer. Each customer gets their own IBAN in the deposit screen; any payment to it belongs to that customer, so references stop mattering. Providers send a webhook for each incoming payment with the payer’s name and IBAN, which makes the own-name check automatic.

This is the rail most new European exchanges try first, for three reasons: it removes the reference problem, it scales without operators, and EMIs are often more willing than banks to take crypto businesses. The trade-offs:

  • The provider is a single point of failure. If it stops serving crypto clients, every customer’s deposit IBAN changes at once. Keep a second provider in onboarding, and design the deposit screen so that switching IBANs is a configuration change, not a release.
  • Provider types differ. Some providers’ virtual accounts accept only first-party payments, from an account in the customer’s name; others accept any payer. Ask which, because it decides whether you need your own name check.
  • Your KYC is checked by theirs. The provider will review your onboarding, your transaction monitoring and sometimes individual customers. Expect questions on deposits that look like pass-through.

Rail 3: a PSP with pay-by-bank and local rails

A PSP gives you a payment page or API and settles the money to your account later. For an exchange, the useful methods are bank-based: open-banking payment initiation under PSD2 in Europe, where the customer approves a transfer in their own banking app, and local real-time rails in markets such as Türkiye, Brazil or India through a PSP licensed there.

The PSP’s payment ID arrives in a webhook, so matching is automatic, and the payment is a credit transfer, so chargebacks do not apply. What changes is settlement: the money sits with the PSP for an agreed period before it reaches your account. Your ledger has to show three states for each deposit (initiated, confirmed by the PSP, settled to the bank), and the customer is usually credited at the second, which means you carry the PSP’s settlement risk for that period.

Card acquiring through your own merchant account is technically the same integration but a different business. Acquirers generally treat crypto purchases as high-risk, and a disputed card payment for crypto that has already been withdrawn is a loss. Most new exchanges leave card payments to a partner.

Rail 4: a card on-ramp partner

A card on-ramp partner sells crypto to the customer by card or local payment method and delivers it to the customer’s deposit address on your exchange. The partner is the merchant of record: it runs its own KYC for the purchase, takes the card risk and the chargebacks, and charges the customer a fee. You embed its widget, pass the deposit address and the asset, and receive a normal blockchain deposit.

The fees are visible to your customer and are the main objection. MoonPay, for example, states in its US pricing disclosure a fee of up to 4.5% and a minimum fee of up to $3.99 on small transactions, rising to up to $4.50 when the customer comes through a partner such as an exchange, with higher minimums in some non-USD currencies (MoonPay pricing disclosure, read 11 November 2026). The customer’s card issuer may charge on top. Fees differ by provider, method and country; compare them on the provider’s own pages before you choose.

What the card on-ramp does not give you is a fiat balance. A customer who wants to sell back to euros needs an off-ramp, from the same partner where it offers one, or one of the first three rails.

What the exchange software must do on any rail

The rails differ in their contracts; the software work underneath is the same. A checklist for your vendor or your own team:

  1. A ledger account per bank and per provider. Each rail has its own asset account, so the exchange can prove at any moment how much customer money is at which institution. Fees per bank (a fixed cost, a percentage or both) post as their own accounting entries, not netted into the deposit.
  2. A matching rule and an exceptions queue. Automatic credit when reference, amount and name match; a queue for everything else, with return as a one-click action that leaves an audit record.
  3. Own-name checks on deposits and withdrawals. Compare the payer or payee name with the verified KYC name, with a tolerance rule for spelling and a manual review for near misses. For withdrawals, the destination account is added like a crypto address: verified once, with a delay before first use.
  4. Withdrawal approvals. Fiat withdrawals above a threshold go through a second person, as crypto withdrawals do. The approval and the bank’s execution reference are stored together. Our admin panel guide covers the queue and the roles.
  5. Daily reconciliation. Ledger balance per institution against the bank or provider statement, with differences listed and explained. Auditors and regulators ask for this report; produce it from the system, not by hand.
  6. Transfer data. In the EU, Regulation (EU) 2023/1113 requires payer and payee information to accompany transfers of funds as well as crypto-asset transfers. Store the payer data that arrives with each fiat deposit with the transaction, not only in the bank portal.

Which rail first?

There is no single answer; it depends on the licence, the market and the customers. These are the patterns we see:

  • Licence granted, European retail customers: virtual IBANs from an EMI as the main rail, a card on-ramp partner for first purchases, a second EMI in onboarding.
  • Licence pending: a crypto-only launch with a card on-ramp partner, where the licence and business plan allow it, and bank talks running in parallel.
  • A broker adding crypto: reuse the broker’s existing client-money accounts and PSP if the bank and the regulator agree that crypto flows may run through them; ask both before building.
  • A local market with its own rails (TRY, BRL, INR): a local PSP or bank for the domestic rail, because international EMIs rarely cover it.

Whatever you choose, start the bank and provider applications early. The integration is weeks; the onboarding is months, and it is the part you do not control. The build guide puts an in-house fiat rail at two to four months of engineering per rail, before any onboarding delay.

What fiat rails cost

There are three cost lines: the software, the provider and your operations time.

Software. At BitPolaris the fiat rails module is €1,700 one-time on the self-hosted or source-code licence, or €85 a month on the cloud model. The card on-ramp module is €840 one-time or €50 a month. EUR and TRY bank-transfer rails exist in the software; other currencies and fiat ramps beyond EUR and TRY are quoted per project, because each provider’s API and statement format is different. Prices are in EUR excluding VAT, from the pricing page on 11 November 2026.

Provider. Banks, EMIs and PSPs charge account fees, per-transaction fees and sometimes a percentage; card on-ramp partners charge the customer. These are set in your contract and change by country and volume; we do not quote them here.

Operations. The exceptions queue and the daily reconciliation need a person. Virtual IBANs and PSP webhooks shrink the queue; a reference-based bank account grows it with volume.

Crypto exchange fiat on-ramp FAQ

What is a fiat on-ramp for a crypto exchange?

It is the way customers move money from a bank account or card into the exchange: a bank transfer to the exchange’s account, a virtual IBAN, a PSP payment such as pay-by-bank, or a card purchase through an on-ramp partner that sends the crypto to the customer’s deposit address.

Do I need a bank account to run a crypto exchange?

You need one for the company and usually for capital, and you need a bank, EMI or PSP to hold customer fiat if you offer fiat deposits. A crypto-only exchange with a card on-ramp partner can launch without a client-money account where the licence and business plan allow it.

What is the difference between a virtual IBAN and a normal bank account?

A virtual IBAN is an account number that routes payments into one master account but identifies a single customer. The exchange gives each customer their own IBAN, so payments match automatically without a reference.

Who carries the chargeback risk on card deposits?

On a card on-ramp partner, the partner does, because it is the merchant of record. On your own card acquiring, you do. Bank transfers and pay-by-bank payments are credit transfers and are not charged back the way card payments are.

Does the exchange software include the bank connection?

The software holds the ledger accounts, matching, approvals and reconciliation; the bank, EMI or PSP contract is yours. BitPolaris runs EUR and TRY bank transfers on the reference exchange and connects other providers per project.

BitPolaris builds the exchange software with fiat rails, a card on-ramp module and an operations console for matching, approvals and reconciliation. It runs on our cloud, your servers or from source, with public prices.

See the Exchange block · Pricing

Sources

  1. Regulation (EU) 2024/886 on instant credit transfers in euro, Articles 5a(8) and 5c(9), EUR-Lex, read 11 November 2026
  2. Regulation (EU) 2023/1113 on information accompanying transfers of funds and certain crypto-assets, EUR-Lex, read 11 November 2026
  3. Directive (EU) 2015/2366 on payment services (PSD2), EUR-Lex, read 11 November 2026
  4. MoonPay USA LLC, Pricing disclosure, read 11 November 2026

Exchange software already in production

Spot trading, liquidity mirroring and the operations console. Cloud from €1,600/month, self-hosted from €24,500 one-time.