01
Frontend Acquiring
- Leveraging Canada MSB and Hong Kong MSO licence qualifications
- Credit card or fiat acquiring based on real trade service scenarios
- Using standard commercial MCC codes (e.g. 5999) to ensure acquiring channel compliance
Solutions
Decoupled Acquiring &
Compliant Payout Architecture
Built on real trade service scenarios, connecting fiat acquiring with compliant payouts through a physically isolated architecture, ensuring clear licence boundaries and audit trails for every fund flow.
Architecture Overview
Three-Stage Decoupled Flow
02
Fund Parking
- Fiat funds cleared to dedicated virtual accounts (VA)
- Funds characterised as "fiat revenue lawfully owned by merchant/client"
- Physical isolation and temporal buffer between fiat and crypto flows
03
User Decision & Routing
- Fiat path: Client chooses fiat, MSO executes standard fiat remittance：
- Crypto path: Client chooses stablecoin, redirected to licensed OTC (OSL / MetaComp)：
- MSO only transfers VA funds to OTC trust account per instruction; OTC handles conversion
Detailed Process
Four Clear Stages
Business Verification
KYB enterprise due diligence, UBO identification, trade document cross-verification
↓Fiat Acquiring
Bank cards, bank transfers, local payments with order matching, clearing and reconciliation
↓Compliant Routing
Sanctions screening, transaction monitoring, 24-hour aggregation, routing to qualified partners
↓Settlement Execution
Licensed OTC independently executes conversion, returning auditable settlement status
Use Cases
Who It's Built For
Multi-currency acquiring
Global player payouts
Compliant cross-border settlement
On-chain payment access
MSO handles fiat flows only throughout the entire process — no virtual asset involvement
Compliance obligations executed by licensed institutions; platform provides technical routing only