Guide3 min readUpdated

    Taking payment in the conversation

    The agent can collect payment in the same thread as the order, so the customer never moves to another channel.

    Payments in the workspace: the Stripe connection, and what stays with a person.

    Four ways to collect

    Payment link (Stripe or a local gateway). The agent sends a link for the exact amount. When the payment clears the agent is told immediately and moves the order or booking forward by itself — nobody has to check and confirm. Best when you want the order to progress without anyone watching for payment.

    Static QR, including DuitNow. Your existing fixed merchant QR is sent in the chat. The amount is not embedded in a static QR, so the customer enters it themselves. Payment is confirmed by a person or by a slip check, never automatically. Best when you already have a merchant QR and want no new provider.

    Dynamic QR. A per-order code with the amount already filled in. This is not something we can switch on alone — your bank or payment provider has to expose it on your account. Tell us who your provider is and we will confirm whether it is available. Best when customers keep typing the wrong amount.

    Payment slip checking. The customer uploads a transfer slip and the agent reads it and matches it against the order. This is what makes a static QR workable at volume — you are not comparing bank notifications by hand. Pairs with static QR and bank transfer.

    Customer pays inside the chat Payment link Stripe / local gateway Confirmed automatically order moves on — nobody watches Static QR / transfer DuitNow — amount typed by hand Slip read & matched mismatch → a person, never auto WHAT DECIDES AUTOMATION IS HOW PAYMENT IS CONFIRMED — NOT WHETHER THERE IS A QR
    What decides automation is how payment is CONFIRMED. A link confirms itself; a static QR is confirmed by slip checking — and a mismatch always goes to a person.

    Static QR and dynamic QR are not the same thing

    Settle this before anything is built. It decides what the customer has to do, and whether confirmation can be automatic.

    Static QR Dynamic QR
    Amount Not embedded — customer types it Pre-filled per order
    Confirmation A person, or a slip check Automatic
    Needs your provider No Yes — they must expose it
    Available today Yes, with your existing QR Depends on your account

    If you have seen a demo where a QR appeared per order, check which of the two it was. A static QR shown alongside an order total still requires the customer to enter the amount.

    The Stripe row in the Integrations table
    1 Stripe, connected. 2 Payments, invoices and refunds sync — refunds sync in so a person can act on them. 3 Live status.

    What always goes to a person

    • Refunds. Money going back out always escalates
    • Disputed or duplicate payments
    • Discounts and prices that are not on your published list
    • Anything where the slip does not match the order amount

    The agent can cancel and reschedule on its own. It does not process refunds — it collects the details and hands the conversation to your team.

    Frequently Asked Questions

    Can the agent take payment without a payment provider?

    Yes, with a static QR and slip checking. That is the route most businesses start on, because it uses the merchant QR you already have and needs no new account.

    Does the customer leave WhatsApp to pay?

    With a payment link they open the gateway page and come back. With a QR they stay in the thread entirely.

    Who is responsible if a payment is missed?

    Slip-checked payments are matched by the agent and flagged when they do not reconcile. Anything that does not match goes to a person rather than being confirmed automatically.

    Still need help?

    Our team is available Mon–Fri, 10 AM–6 PM MYT (GMT+8).

    Contact support