Compliance Center

Regional Readiness

VSL serves users across Nigeria, Kenya, Ghana, South Africa, the European Union / EEA, the United Kingdom and Canada. Each market now has its own compliance page so privacy, payments, identity, consumer protection and provider availability can be explained in the correct local context.

Nigeria Kenya Ghana South Africa EU / EEA United Kingdom Canada
Regional approach: VSL separates service availability from provider availability and legal authorisation. Each regional page explains the controls VSL applies, the provider dependencies that affect a feature, and the local framework VSL evaluates. Provider onboarding is not presented as a VSL licence or blanket regulatory approval.

Choose a market

Open the dedicated page for the country or region you want to review.

How VSL reads regional availability

Being available in a market does not mean every payment rail, payout method or regulated capability is available there.

VSL service availabilityVSL enables marketplace, RFQ, social-commerce, payment-request, delivery and business-management features by market and product readiness.
Provider availabilityFincra, Busha, NOWPayments, banks, card networks and other providers determine the countries, currencies, merchant types and transaction purposes they support.
Regulatory classificationVSL keeps regulated custody, payment, money-services and virtual-asset functions provider-led. VSL separately evaluates any feature that could change VSL's own regulatory role.
User obligationsSellers and buyers remain responsible for the legality of the goods or services, taxes, customs, licences, representations and transaction purpose.

Regional launch gate

VSL applies the same evidence-based review whenever it enables a sensitive capability in a new market or changes a provider or payment rail.

GateWhat VSL documents and can evidence
Role and authorisationVSL records the exact role it performs in the feature and whether the activity requires additional authorisation, a regulatory filing, a local representative or provider approval.
PrivacyVSL identifies the applicable privacy framework, necessary data, purpose, lawful basis where required, recipients, transfers, retention and user rights.
Provider capabilityVSL verifies that the provider supports the country, currency, merchant type, payout route, identity method and transaction purpose before exposing the capability.
KYC / AML / sanctionsVSL documents the identity or KYB information required, the provider or party performing screening, and the escalation path for failed or enhanced checks.
Marketplace / consumerVSL maps seller traceability, prohibited-goods, product-safety, pricing, refund, warranty and complaint requirements to the relevant market.
AIVSL evaluates whether a feature needs additional transparency, consent, confirmation, human oversight, logging or another market-specific control.
Security / incident responseVSL keeps access control, logging, provider-webhook security, edge protection, incident ownership and breach-response procedures aligned with the workflow.
OperationsVSL confirms the support, dispute, legal-escalation, provider-contact and suspension/recovery path for the market.