Off-ramp and withdrawal to fiat
1) Why off-ramp in iGaming
Off-ramp turns the operator's crypto assets into fiat payments to players/partners and replenishes the company's fiat accounts. Objectives:- fast and predictable outputs (T + 0/T + 1),
- reduced volatility (T0 conversion),
- compliance with AML/sanctions/Travel Rule and requirements of banks/PSP,
- transparent accounting and taxation.
2) Off-ramp models
2. 1 Custodial (via VASP/processor)
The provider holds wallets, makes TAC/sanctions, converts and sends fiat to the bank/payout provider.
Pros: integration speed, SLA, built-in compliance. Cons: addiction, fees, limits.
2. 2 Noncostodial (own wallets)
You control the keys, send assets to the exchange/broker, convert and withdraw fiat.
Pros: flexibility, control of commissions/routes. Cons: operational risks, need for treasury 24/7.
2. 3 Hybrid
Custodial flow for mass amounts/regions, independent - for VIP/special assets/peak loads.
3) Fiat payment rails
SEPA/SEPA Instant (EUR): Cheap/fast in the EEA.
Faster Payments (GBP), ACH/RTP (USD): local low-cost channels.
SWIFT: Crossborder, more expensive and longer, needed for many countries.
Local schemes: Pix (BR), UPI/IMPS (IN), M-Pesa/mobile money (Africa), vouchers/wallets (LATAM/Asia).
Card payments (OCT/Push to Card): pseudo-instant to the card, limits/geo-restrictions.
4) Payout/Disruption Providers
Functions: creation of payment packages, CC/recipient sanctions (where required), verification of details, statuses, webhooks, evidence (UTR/ARN).
Selection criteria: coverage of countries/methods, limits, commissions, uptime, SLA, support speed, reporting quality.
5) Compliance core off-ramp
Player KYC: sufficient tier (ID/showers; PoA/SoF by triggers).
SoF/SoW: for large conclusions/anomalies (rapid in-out, structuring).
KYT (crypto): risk assessment of addresses/routes before conversion and during output.
Travel Rule: VASP↔VASP exchange of IVMS101 for on-chain outgoing before off-ramp (where applicable).
Sanctions/REP: daily rescreen of clients/counterparties.
RBA matrix: Low/Med/High → different depth of checks, limits and speed.
6) Limit policies and solutions
Gain triggers: PEP/adverse media, high-risk geo, new details, fast depozit→vyvod, split amounts.
7) Treasury, FX and Liquidity
T0 conversion of crypto → stable/fiat when creating an application (or T + N by policy).
RFQ/multibiergie: choose the best course, take into account commissions and slippages.
Liquidity pools: working float on VASP/exchanges, output limits, multisig and 4-eye rule.
FX policy: price source (multi-feed), fixing time, rounding and returns rules.
8) Flows and statuses (reference)
1. The player requests the output of → 2. RBA/KYT checks/sanctions → 3. Conversion (if necessary) → 4. Formation of payment (rail/provider) → 5. Send/Confirm (UTR/ARN/SRN) → 6. Delivery to the player → 7. Post-control (notifications, reports, reconciliation).
Statuses for UX: 'Accepted' → 'Under Review' → 'Paid to bank/provider' → 'Credited '/' Delay '/' Rejection'.
9) Reconciliation and Accounting
Мэппинг: `withdrawal_id ↔ txid(on-chain) ↔ conversion_id ↔ bank_reference`.
Reconciliation T + 0/T + 1: amounts, network/provider commissions, FX, statuses, open balances.
Ledger & DWH: two-way transactions, wallet/account inventory, immutable logs.
Taxes/reporting: downloads by jurisdiction, storage of the primary ≥ terms of the law.
10) UX output (without breaking conversion)
Transparent dates (dynamic ETA by method/region).
Verification of details (IBAN/card) and error warnings.
Split payments/partial release under EDD/SoF.
Journal: receipts, links to payment, help "where to go."
Quiet hold: timers/reason ("confirmation of the source of funds is required"), button for downloading documents.
11) Returns and disputes (disputes)
No chargebacks as in cards: return = new payout/return to original source (where possible).
Address/account policy: returns only to previously verified details.
Playbook: lost payments (investigation with the bank/provider), incorrect details (cancellation/return according to the regulations), currency/exchange rate conflict (fixing rules).
12) SLA, uptime and degradation
SLA landmarks: Low Risk auto cases - ≤ 15 min p95, Medium - ≤ T + 1, High/EDD - ≤ 24-48 h.
Payment provider uptime ≥ 99. 9%, webhooks ≤ 2-5 with p95.
Degradation: rail delays (RTP/SEPA Inst down) → auto-protection switching/standard SEPA/SWIFT; growth of'R-codes '/reject → tighten the validation of details; KYT incidents → hold + SoF.
13) Metrics and OKR
Payout Success Rate, Time-to-Payout p50/p95, SLA hit rate.
Cost per Payout (all-in: provider + rail + FX + network).
KYT reject %/sanctions hits/SAR-conversion.
Hold/EDD fraction, average unlock time.
UX: share of incorrect details, repeated requests for documents, NPS/CSAT by conclusions.
Reliability: uptime, webhook speed, feilover frequency.
14) Anti-patterns
The only provider/rail without a feilover.
Lack of T0 conversion - losses from volatility.
Payments for unverified details.
Ignoring KUT/sanctions "due to small amounts."
No idempotency - duplicate payments in case of retrays.
"Deaf" locks without partial release and understandable communication.
15) Implementation checklist (short)
- RBA Policy: Limits/Triggers, PoA/SoF/SoW, PEP/Sanctions, KYT/Travel Rule.
- Payout provider (s) + reserve, track by region (SEPA/FPS/ACH/SWIFT/local/Push-to-Card).
- Treasury: T0-conversion, RFQ/multibiergi, multisig, limits, 4-eye.
- Validation of details (IBAN/BIC/card BIN), anti-duplicates, idempotent keys.
- Statuses/webhooks, proofs (UTR/ARN), dashboards, and SLA alerts.
- Accounting/Reconciliation: Ledger, Mapping 'withdrawal↔txid↔bankRef', Reporting/Taxes.
- UX: ETA, partial release, clear hold reasons, document portal.
- Incident playbooks: rail failures, incorrect details, KYT high-risk, sanctions.
- Support/finance/compliance training; letter and response templates.
- Quarterly metrics reviews and A/B calibration of limits/thresholds.
16) Summary
A successful off-ramp in iGaming is a payout architecture, not one provider: multi-rails and a failover, strict RBA + KYT/sanctions/Travel Rule, T0 conversion and treasury discipline, transparent UX and idempotent technique. Such a circuit provides quick and predictable conclusions, reduces cost and keeps risks under control.