Compliance Reference
Swipelux operates as an EU-licensed Virtual Asset Service Provider (VASP). This section explains the compliance model, supported jurisdictions, onboarding requirements, payment methods, and responsibility split between Swipelux and sub-merchants.Topics
General Information
Understand Swipelux’s role as the regulated entity and how compliance responsibilities are split with sub-merchants. General Information ->Supported Verticals
See how business categories are classified into allowed, conditional, and prohibited risk tiers. Supported Verticals ->Jurisdiction Framework
Review end-user eligibility by region, document requirements, payment rail availability, and transaction limits. Jurisdiction Framework -> Transaction Limits ->End-User Identity Verification (KYC)
Review individual KYC paths, including standard verification and approved reliance flows. KYC Verification -> Implementation: Individual onboarding API workflowWallet Architecture and Payouts
Understand custodial MPC wallets and self-custody withdrawal controls. Wallet Architecture ->Payment Methods
See supported pay-in and payout methods. Payment Methods ->Merchant Onboarding (KYB)
Review KYB requirements, document collection, and Enhanced Due Diligence triggers. Merchant Onboarding -> Implementation: Business onboarding API workflowTravel Rule Compliance
Understand FATF Recommendation 16 controls for VASP-to-VASP transfers and unhosted wallet transactions. Travel Rule ->Screening and Monitoring
Review sanctions, PEP, blockchain analytics, and transaction monitoring controls. Screening and Monitoring ->Governance and Roles
See how Swipelux and sub-merchants split responsibilities, including data retention. Governance ->Quick Reference
Swipelux Responsibilities:- KYC, sanctions, PEP screening
- Wallet screening, blockchain execution
- Crypto custody and exchange
- Travel Rule compliance
- Marketing compliance
- UX geoblocking
- Sector-specific licensing
- User journey design