Accept payments wherever your customers are

Accept payments from anyone, anywhere.

Accept payments in person, through WhatsApp, Facebook or AI agents, or on your own platform with VSL’s embedded payment system. Keep the request and payment status in one transaction session.

Explore the three ways Read the VSL overview
Choose how your customer pays
  1. OnlineShare a payment request and receive money remotely.
  2. OfflineCollect in person with supported QR or POS-style tools.
  3. EmbedAdd a supported VSL checkout or payment action to a site or blog.
  4. ConnectUse more than one channel for the same business.
Channel guide

Accept, receive and make payments with VSL.

Choose how to receive money or open a VSL user’s payment request. Confirm the recipient, reason, amount and currency before payment.

Online, offline, and embedded VSL use

  • Accept and Receive Payments Online

    Receive payments remotely through a VSL request or link shared in a conversation, WhatsApp, Facebook, email or another supported online channel.

    Agree the reason, amount and currency, then share the official VSL payment request. The person paying chooses an available payment method.

    Use online payment requests for products, services, fees, invoices or other lawful agreed transactions. To pay a VSL user, open their official request, check the recipient and amount, then keep the transaction reference.

    Good practice: confirm the item or service, amount, currency, customer, delivery or fulfilment terms, refund expectations, and final payment status before treating the order as paid.

  • Accept payments face to face at a shop, market, event, appointment or another supported setting.

    Present your supported VSL payment link, QR code or virtual POS. The person paying completes an available card, bank transfer, USDT or BTC payment, and you review its recorded VSL status.

    For a cash payment, receive the money directly from the person in front of you. This is separate from a digital payment processed through VSL.

    Good practice: confirm the correct amount and currency on both sides, protect the device or QR display from tampering, and verify the completed payment inside the supported VSL flow.

  • Use VSL’s supported embedded payment system to receive payments on your own website or platform.

    Place your official VSL payment action beside the transaction details, or link a clear payment button to your VSL payment request.

    Explain the reason, recipient, amount and currency, along with any service, delivery or refund terms that apply. People can then pay without starting in the VSL marketplace.

    Good practice: use only the official VSL embed, checkout, or payment-link details assigned to the account. Do not copy receiving details from an unverified message or expose private credentials in website code.

  • Use VSL to accept payments wherever the interaction begins: online, face to face, through WhatsApp, Facebook, personal or anonymous AI agents, or on your own platform.

    The same payment purpose can be supported across different channels. A professional can request a fee in a chat, share a link by email or present a supported QR code at an appointment.

    Keep your name, amount, currency, payment reason and contact details consistent so the person paying knows whom the request is for.

  • Recommended sequence
    Move a remote customer from agreement to payment.

    Use this workflow for online enquiries, quotes, invoices, payment requests, and shareable VSL payment links.

    Online payment
    1. Explain the payment

      State what the payment is for and who should receive it.

    2. Confirm the payment details

      Agree the recipient, reason, amount and currency, plus any relevant terms.

    3. Create the request

      Prepare the appropriate quote, invoice, or payment request.

    4. Share the VSL action

      Send the supported VSL payment link or payment action to the customer.

    5. Verify before fulfilment

      Check the recorded VSL payment status before providing the goods or service.

    Completion check: the transaction details are correct and VSL shows the recorded payment status.
  • Recommended sequence
    Collect an in-person payment with a clear handoff.

    Use this workflow for shops, markets, events, deliveries, appointments, and other supported QR or POS-style transactions.

    In-person sale
    1. Select the payment request

      Enter or open the request for the amount you are receiving.

    2. Confirm the total

      Review the amount and currency with the customer before payment begins.

    3. Present the payment option

      Show the supported VSL QR or POS-style payment option.

    4. Let the customer complete it

      Allow the customer to finish the payment without exposing private information.

    5. Verify and fulfil

      Check the final VSL payment status, then provide the agreed goods, service, or receipt.

    Completion check: the VSL payment status is confirmed before the customer leaves with the goods or service.
  • Website setup
    Build the page first, then place the VSL payment action.

    Keep the offer, payment button, customer expectations, and VSL transaction details in one clear journey.

    Website or blog
    Best used on Product pages, service pages, booking pages, campaign pages, articles, and other pages where a customer is ready to pay.
    1. Explain the offer

      Explain the payment reason and identify the person or business receiving it.

    2. Show the important terms

      Place the price, currency, delivery or fulfilment expectations, refund terms, and seller contact details near the payment action.

    3. Place the official VSL action

      Add the supported VSL payment action where the person is ready to pay.

    4. Use a direct button label

      Use clear wording such as “Pay with VSL” or “Continue to VSL Checkout” so the next action is obvious.

    5. Test and keep details matched

      Test the full journey on desktop and mobile, then confirm the page matches the VSL amount, currency, and fulfilment information.

    Publish check: customers can understand the offer, find the payment action, and see what happens after payment without searching elsewhere.

  • For online, in-person and embedded payments, keep a clear record of the person paying, the recipient, the reason, the amount, the currency and the payment status.

    Quotes, invoices, payment requests, receipts, order information, and messages can help both sides understand what was agreed. Records support reconciliation and customer service, but users remain responsible for their own accounting, tax, legal, refund, and fulfilment duties.

  • Use lawful products and services, accurate descriptions, correct payment details, and official VSL tools. Never place secret keys, private credentials, passwords, or sensitive account information in public website or blog code.

    Do not treat a screenshot, verbal claim, or customer message as final proof of payment. Confirm the status through the supported VSL record. Review suspicious, reversed, failed, delayed, or disputed transactions before fulfilment.

Quick reference

Choose the right VSL channel.

Accept payments wherever your customer is, with one VSL transaction session linking the request, payment status and related records.

Online

Receive money remotely through payment requests and links shared by chat, email, WhatsApp, Facebook or supported AI agents.

Offline

Receive digital payments face to face through supported VSL links, QR codes or virtual POS tools.

Embedded

Receive payments on your own website or platform through VSL’s enabled embedded payment system.

Combined

Use several channels to accept payments while keeping the request, amount and payment status connected.

Confirm before fulfilment

Check the amount, currency, customer, transaction reference, payment status, and order or service details before releasing goods or completing work.

Availability and compliance

Features vary by region, account eligibility, verification, payment partner, transaction type, device support, risk review, and applicable law.