100+
Fiat currencies
100+ fiat currencies including USD, EUR, GBP, INR, NGN, BRL, TRY, VND, PHP, IDR and AED. Operators activate options per market, and each currency carries its own spread, limits and settlement.
USDEURGBPINR
FIAT ON-RAMP & OFF-RAMP
Fiat On-Ramp and Off-Ramp Infrastructure, Running Under Your Brand
The Fiat On-Ramp & Off-Ramp is white-label infrastructure for fiat-to-crypto and crypto-to-fiat flows via cards, bank transfers, and regional payment methods, with routing across integrated licensed payment providers. Your users buy and sell with the money they already have, inside your product, on your pricing — and every order is routed to the provider most likely to approve it.
- Buy with a cardDebit and credit card purchases on the major networks, quoted and branded by you, with fraud and chargeback rules applied before the charge is attempted.
- Fund by bank transferSEPA, Faster Payments, ACH and local bank rails for the users who will not put a large purchase on a card — matched to the deposit automatically.
- Pay the local wayUPI, Pix, GCash, mobile money and the other methods a market actually uses, switched on per country and currency instead of shipped everywhere at once.
- Cash out to a bank accountThe off-ramp sells at a locked quote and pays the proceeds to a verified bank account or local method, with screening and limits before the instruction leaves.
100+Fiat currencies
500+Payment methods
Multi-providerRouting with failover
THE RAMP FLOW
Quote. Verify. Route. Deliver. Reconcile.
The full path a fiat order takes on your platform, in both directions — from the moment a user asks what a purchase will cost to the moment finance ties the provider's settlement file back to the order.
1
QUOTE
The user picks a direction, a fiat currency and a payment method you enabled for their market. The platform returns one quote — rate, your spread, provider fee and the amount that will arrive — and locks it.
2
VERIFY
Before money moves, the order is checked against the KYC tier reached, sanctions and PEP screening, fraud rules for the method, and the per-user caps you set per market. Tiers and limits are per jurisdiction.
3
ROUTE
Routing narrows to providers that support the currency and method, applies your priority order, compares landed cost, and weighs outcomes recorded for that region. A decline fails over without the user restarting.
4
DELIVER
On the on-ramp, the purchased asset is credited to the wallet as soon as payment confirms at your depth. On the off-ramp, the sale settles and the payout goes to the provider paying the user’s bank account.
5
RECONCILE
Each provider settlement file is matched back to the orders that produced it, line by line, so fees, spread, refunds and chargebacks land against the original order. Breaks are queued rather than absorbed.
One Routing Layer Between Your Users and Every Provider
Each stage below is a real subsystem in the deployment. Quoting, screening, routing and settlement each have their own controls, and the provider that executes the payment is chosen per order rather than fixed at integration time.
Embedded Widget or White-Label Ramp
Most teams evaluating fiat rails are really choosing between dropping in someone else's checkout and owning the flow themselves. The conclusion of the table below: a widget is faster to switch on but hands the brand, the margin, the provider choice and the customer data to the vendor, while a white-label ramp keeps all four on your side and lets a declined order retry somewhere else.
| # | What you are deciding | Embedded third-party widget | White-label ramp on Coiny |
|---|---|---|---|
| 1 | Brand and interfaceWhat the user sees at the moment of payment | The vendor's checkout in a frameTheir logo, their flow, their support copy | Your product, end to endYour brand, copy, layout and domain |
| 2 | Customer relationshipWho the buyer thinks they transacted with | Shared with the widget vendorSupport tickets often leave your platform | Yours aloneYour support team sees the whole order |
| 3 | Provider choiceWho actually processes the payment | Fixed by the widgetOne provider, no visibility into selection | Several providers behind routingChosen per order on your rules |
| 4 | Pricing and marginWhere the spread on a purchase lands | Set by the vendorRevenue share at best | Set by you, per marketYour spread and fee schedule |
| 5 | Declines and coverage gapsWhat happens when one provider says no | The purchase failsThe user is asked to try again later | Failover to the next providerWithout restarting the order |
| 6 | Data and reconciliationWhat finance and analytics can see | A vendor report to importLimited order-level detail | Order-level records in your systemsOne reference from quote to export |
| 7 | Licensing of the money legWho is authorised to handle the funds | The widget vendor's providerTerms you do not negotiate | Integrated licensed payment providersProviders carry the licensing, not Coiny |
REGIONAL COVERAGE
The Methods Your Market Actually Pays With
A ramp only converts when the currency, the method and the provider all line up for the user in front of it — so coverage is configured per market rather than shipped as one global default.
500+
Payment methods
500+ regional and global methods, from card networks and SEPA, Faster Payments and ACH through to UPI, Pix, GCash and mobile money. You configure which appear per fiat currency.
CardsSEPAUPIPix
180+
Countries reachable
Users in 180+ countries, with eligible methods, verification tiers and limits differing by jurisdiction. A market needing a new licensed provider takes one without changing your interface.
Per-market rulesProvider failover
RAMP CONSOLEBook a Demo
Configure Every Market Without Shipping Code
One console for the team that owns the ramp: which methods are live where, which provider takes them first, what happens on a decline, and which controls gate a first purchase.
Methods enabled per marketTurn a currency, a method or a region on, off or into review without a release. Each row shows the primary provider and its fallback.
Routing rules you can readOrdered and explicit: coverage, then your provider priority, then landed cost, then recorded approval outcomes, then failover.
Spreads and fees by currencyYour spread, fixed fee and minimum are set per currency and method, and the quote is built from exactly those numbers.
Verification tiers and limitsKYC tier gates, sanctions and PEP screening and per-user caps are configured per jurisdiction, so one deployment meets several markets.
Refunds, chargebacks and breaksRefunds run against the original order reference, chargebacks open a case with evidence, and unmatched settlement lines are queued.
Provider failover you controlSet the fallback order per currency and method, so a provider outage moves traffic to the next eligible one instead of a dead screen.
How Each Rail Is Routed and Settled
Provider routing is not one rule applied to everything. The conclusion of the matrix below: each rail is selected on different evidence and settles on a different clock, and in every case an integrated licensed payment provider — not Coiny — executes the money leg.
| # | Rail | How routing decides | Settlement and timing | Licensing and controls |
|---|---|---|---|---|
| 1 | Card on-rampDebit and credit, major networks | Approval likelihood for the region and card type, then landed costFailover on decline or timeout | Crypto credited on payment confirmationProvider settles to your account on its cycle | Card provider is the licensed processorFraud, 3-D Secure and chargeback rules apply |
| 2 | Bank transfer on-rampSEPA, Faster Payments, ACH and local rails | Currency and rail coverage first, then your priority orderOne provider per rail in most markets | Credited when the deposit is matched to the orderSame-day to a few business days by rail | Bank settlement partner holds the accountReference matching and unmatched-deposit queue |
| 3 | Regional payment methodUPI, Pix, GCash, mobile money and similar | Whether the method exists in that market at allRegional acquirer per country | Usually near-instant confirmationProvider settles in local currency | Regional acquirer holds the local licensingPer-market caps and tier gates |
| 4 | Crypto-to-fiat off-rampPayout to a bank account or local method | Destination country, currency and payout method supportCost and payout speed compared | Sale settles, then the payout instruction is sentArrival follows the destination rail's clock | Payout provider executes the bank settlementScreening and named-account checks first |
| 5 | Refunds and chargebacksMoney going back the way it came | Always returned through the original providerNever re-routed to a cheaper one | Booked against the original order referenceVisible in the same statement line | Provider dispute process, your evidence packCase opened automatically on notification |
Everything a Ramp Has to Do Besides Take the Payment
Accepting a card is the easy half. What decides whether a ramp is worth owning is the quoting, the screening, the routing and the settlement trail sitting behind it.
QUOTING
Quotes, rates and fees you control
One quote object covering rate, your spread, provider fee and the net amount that will arrive, locked for a window and identical in the interface, the API and the receipt.
- Locked quote window with explicit expiry
- Per-currency and per-method spread and fees
- Same quote in the UI, the API and the receipt
METHODS
Cards, bank transfers and regional methods
Cards on the major networks, bank rails including SEPA, Faster Payments and ACH, and the regional methods a market uses — each enabled per currency and country, and pausable on its own.
- Card, bank transfer and local method rails
- Enabled per country and per currency
- Pause a single rail without downtime
ROUTING
Provider routing with failover
Orders are matched to providers that can serve them, ordered by your priority rules, landed cost and recorded approval outcomes. Adding a provider is configuration, not a rebuild.
- Coverage, cost and approval-outcome rules
- Automatic failover inside the same order
- Add a provider without changing the UX
COMPLIANCE
Verification tiers, screening and limits
KYC tiers gate what a user may transact, sanctions and PEP screening runs before the money leg, and per-user caps apply per market. Every decision is logged with its reviewer.
- Tiered verification with per-jurisdiction rules
- Sanctions and PEP screening before payment
- Audit-ready log of every decision
SETTLEMENT
Settlement, refunds and reconciliation
Provider settlement files are matched to orders line by line, so fees, spread, refunds and chargebacks resolve against the order that caused them. Unmatched lines are queued.
- Line-by-line provider settlement matching
- Break queue instead of silent write-offs
- Accounting export on one reference
CONNECTED PRODUCT
stablecoin settlement rails
Where settlement should stay digital rather than land in a bank account, the ramp hands off to the stablecoin payments and treasury layer. Fiat conversion is this page’s job.
- Stablecoin acceptance and merchant settlement
- Multi-wallet treasury with approval quorums
- Off-ramp handoff where local currency is needed
APIS
Ramp APIs and webhooks
REST endpoints for quotes, orders, limits and payouts, plus signed webhooks on every state change, with idempotency keys, scoped keys and an isolated test environment.
- Idempotent quote and order creation
- Signed webhooks on every state change
- Isolated test environment before go-live
OPERATOR QUESTIONS
What Product and Finance Teams Ask Before Owning the Ramp
- What happens when a card is declined in one market?The order is not lost. Routing narrows to the providers that still support the currency and method, applies your priority order, and retries on the next eligible provider inside the same order rather than sending the user back to the start. Where every eligible provider declines, the user is offered the bank transfer or regional method you have enabled for that market.
- Do we keep the spread, or does the provider set it?You set it. Your spread, fixed fee and minimum are configured per currency and per payment method, and the quote the user sees is assembled from those values plus the provider's own charge, shown explicitly. The provider is paid its fee for executing the payment leg; the pricing decision and the resulting margin stay with the operator.
- Can we add a provider later without rebuilding the flow?Yes. Providers sit behind the routing layer rather than in the interface, so adding one is configuration: declare the currencies, methods and countries it serves, put it in the priority order, and it starts taking orders. The user-facing quote, checkout and receipt do not change, and existing orders continue on the provider that took them.
- How do we prove at month end that ramp orders and provider payouts agree?Every order carries one reference from the quote through the provider settlement file into the ledger entry and the accounting export. Settlement files are matched line by line, so fees, foreign-exchange spread, refunds and chargebacks resolve against the order that caused them, and anything unmatched is queued for review rather than absorbed into a balancing figure.
- Are we becoming a payment institution by running this?No. Coiny Exchange supplies the ramp infrastructure — quoting, verification, routing, delivery, settlement reporting and the branded interface — and is not a bank, a payment institution, a money transmitter or a licensed custodian. Each fiat leg is executed by an integrated licensed payment provider that holds the money-service licensing in that market, and the compliance tooling is built to support your own licensing process.
RELATED
Where the Fiat Ramp Sits in the Coiny Stack
Fiat conversion is one rail among several. These are the products it connects to most often.
BUILT FOR
Teams Whose Growth Stops at the Funding Screen
The buyer is usually whoever owns onboarding conversion and has watched users abandon at the moment they were asked to fund an account.
Exchange operators adding a fiat gateway
A way in that does not require users to already hold crypto elsewhere, and a way out that does not end at an unsupported withdrawal.
Wallet and fintech product teams
Embed buy and sell inside your own onboarding and wallet screens through the ramp APIs, rather than handing off to a third-party checkout.
Operators expanding into new markets
Enter a country by switching on its currency, local methods and a provider that serves it, with tiers configured for that jurisdiction.
Finance teams who have to explain the numbers
Settlement files matched line by line to orders, a queue for anything that does not reconcile, and one export carrying the quote reference.
COMMON QUESTIONS
FAQ
A crypto fiat on-ramp is the flow that turns a user's ordinary money — a card payment, a bank transfer or a local payment method — into crypto credited to their wallet, and an off-ramp is the same flow in reverse, selling crypto and paying the proceeds into a bank account. Coiny Exchange deploys both as white-label infrastructure: your brand, your quote and fee rules, your interface, with the payment leg routed to integrated licensed payment providers.
Provider routing is the logic that decides which integrated payment provider handles a given fiat transaction instead of sending every order to one supplier. Coiny Exchange evaluates each order against the providers that support the currency and method, then your priority rules, the landed cost of provider fee plus foreign-exchange spread, and the outcomes recorded for that region and card type. A decline or timeout fails over to the next eligible provider without the user restarting.
An embedded ramp widget is a third-party checkout dropped into your product: the vendor owns the interface, the pricing, the single payment provider and the customer record. A white-label ramp is infrastructure you run under your own brand, with your quote and fee rules, several providers behind a routing layer and the transaction data in your own systems. Coiny Exchange deploys the white-label model, which is why declines can fail over and margin stays yours.
Users buy crypto with debit and credit cards on the major networks including Visa and Mastercard, with bank transfers such as SEPA, Faster Payments and ACH, and with the regional methods their market actually uses — UPI, Pix, GCash, mobile money and local bank rails among them. The Coiny Exchange platform supports 100+ fiat currencies and 500+ payment methods, and the operator switches on the subset that suits each market.
A crypto-to-fiat off-ramp sells the user's crypto at a quoted rate, then pays the fiat proceeds out through a payment provider to the bank account or local method the user has verified. On Coiny Exchange the sale, the quote lock and the payout instruction all carry one reference, screening and limits apply before the instruction leaves, and the bank settlement itself is executed by an integrated licensed payment provider.
Fiat ramp transactions are reconciled by matching each provider's settlement file back to the orders that produced it, line by line, so fees, foreign-exchange spread, refunds and chargebacks land against the original order rather than in an unexplained balance. Coiny Exchange keeps one reference from quote through provider settlement to ledger entry, queues anything that does not match for review, and exports the result to your accounting system.
The integrated payment providers are. Coiny Exchange supplies the ramp software — quoting, verification, routing, delivery, settlement reporting and the branded interface — and is not a bank, a payment institution, a money transmitter or a licensed custodian. Each fiat leg is executed by a provider that holds the money-service licensing in that market, and Coiny's compliance infrastructure is built to support the operator's own licensing process rather than replace it.
LAUNCH THE RAMP
See a Fiat Order Routed End to End
Walk through a live deployment — a branded quote with your spread, a tier check and screening, routing across providers with a decline failing over, delivery to a wallet and to a bank account, and the settlement file reconciled back to the order.
Book a Demo