Marketplace Responsibility
VSL provides commerce infrastructure, but users remain responsible for the transaction they create. Sellers are responsible for what they offer and how they fulfil it; buyers are responsible for what they request, the information they provide and the lawfulness of their purchase and payment.
Seller responsibilities
The seller controls the offer and is responsible for the commercial truth of that offer.
- Only offer goods/services the seller is legally permitted and genuinely able to sell.
- Use accurate titles, descriptions, images, quantities, prices, currency, condition, origin and delivery/availability information.
- Disclose material limitations, licences, age restrictions, safety information, warranty/refund rules and other facts the buyer needs before purchase.
- Do not use another person's identity, bank account, payment account, business registration, intellectual property or product images without authority.
- Meet tax, customs, import/export, product registration, consumer, product-safety and sector-specific obligations that apply to the seller or goods/services.
- Fulfil lawful orders, keep delivery/acceptance evidence and respond to legitimate refund, warranty, chargeback or dispute processes.
- Provide accurate KYC/KYB and payout-owner information when a provider or VSL workflow requires it.
Buyer responsibilities
Buyers are not passive from a compliance perspective.
- Use a truthful identity/contact profile where needed to transact, receive a delivery or complete payment verification.
- Do not request illegal, prohibited, sanctioned, stolen, counterfeit or restricted goods/services through VSL.
- Use lawful funds/payment accounts and do not initiate fraudulent disputes, chargebacks or claims.
- Review the seller, item/service, price, currency, delivery terms, refund/warranty terms and material product information before payment.
- Provide accurate delivery/customs information and comply with import, age, permit or local possession/use rules that apply to the buyer.
- Preserve transaction/payment/delivery evidence and raise genuine problems promptly.
What VSL does and does not verify
VSL limits each verification statement to the evidence actually checked.
VSL verifies account identity, payment-recipient details, provider connections, public capabilities or transaction evidence when the relevant workflow requires it. That verification does not mean VSL has inspected every product, audited the seller's entire business, certified product quality or guaranteed future delivery.
Commerce Passport evidence distinguishes seller assertions from VSL-observed or verified signals. Users remain responsible for proportionate due diligence on high-value, regulated, customised or cross-border transactions.
Prohibited and restricted commerce
VSL can refuse platform access or a payment workflow even where a user believes the underlying transaction is legal.
VSL's Acceptable Use rules, payment-provider terms, card/bank/crypto-network rules and local law can each create restrictions. A transaction may therefore be rejected because of the item/service, country, user type, sanctions/AML risk, payment purpose or provider policy.
Where required, VSL can remove or restrict content, stop a payment/payout capability, preserve evidence, suspend an account, seek additional verification or escalate activity to a provider or competent authority.
Consumer, product and cross-border obligations
The applicable rules depend on where the seller and buyer are located, what is being sold, and whether the seller is acting as a trader or business.
- Nigeria: consumer rights and seller representations can be governed by the FCCPA and sector/product rules.
- EU/EEA: trader identification, consumer information, product safety and DSA marketplace duties can apply in addition to national law.
- United Kingdom: UK consumer/product rules apply independently of EU rules after Brexit.
- Canada: VSL's current focus is Toronto/GTA in Ontario and Calgary/Alberta, where provincial consumer rules apply alongside relevant federal requirements.
- Kenya, Ghana and South Africa: local consumer, product, tax and sector rules remain the responsibility of the parties and must be assessed for regulated goods/services.
- Cross-border: seller and buyer can each have customs, export/import, sanctions, tax, licensing or documentation obligations.
Reports, public-content enforcement and private case evidence
VSL can administer public marketplace content while preserving the privacy boundary around seller-customer communications.
Public listings, public profile material, product media and public comments can be reported and reviewed. VSL can restrict, hide, delist or remove public content when it breaches VSL rules, applicable law or creates a material safety, fraud or platform-integrity risk.
Private seller-customer conversations are not public moderation content. VSL reviews relevant private material when one of the participants reports it, opens a dispute or asks VSL to investigate a fraud, safety or support issue. The material remains private and access-controlled during that review.
A report is evidence that requires assessment; it is not automatic proof against the reported user. VSL uses the report together with the relevant commerce, payment, account and delivery evidence before taking a proportionate platform action.
Disputes, refunds and evidence
VSL records can establish what happened on-platform, while legal responsibility depends on the transaction and applicable law.
- VSL can preserve quotes, invoices, messages, payment references, delivery events and other platform evidence relevant to a dispute.
- Payment-provider chargeback/reversal rights can apply separately from a seller's own refund terms.
- A seller cannot use a “no refunds” label to remove statutory consumer rights that apply to the transaction.
- A buyer cannot use a dispute or chargeback system fraudulently after receiving the agreed goods or services.
- VSL provides workflow records, evidence and platform enforcement without guaranteeing the outcome of a court, regulator, bank or provider process.
Regulatory and provider references
Primary regulator, government and provider materials used to frame this public compliance overview. External documents can change; VSL reviews the applicable source before relying on it for a launch or feature decision.