Accepting payments in WhatsApp — cards and wallets right in the chat
Step-by-step setup for in-chat payments: Stripe links, auto-generated invoices, webhooks and CRM status updates. Chat-to-payment conversion +45%.
Why this matters
Picture an online boutique in Austin. A customer messages "I want the $180 jacket, size M". The rep replies with PayPal instructions, the customer asks for the account again, eventually says "sent", the rep checks the bank app, ships the order, forgets to update the spreadsheet. One sale: 15 minutes of back-and-forth.
ZiFlow compresses that to 40 seconds. The AI detects purchase intent, generates an invoice, sends a payment link, listens for the webhook, updates the CRM, and pings the rep. The customer taps the link and pays — chat-to-payment conversion typically jumps 40–50%.
How it looks in the wild
Your rep opens the dashboard in the morning and sees 7 successful payments from overnight — the bot handled everything:
- Customer: "how much is the hydrating cream?"
- Bot quotes the price and asks: "Would you like to order? Shipping within Austin is $8."
- Customer: "yes, 123 Oak St."
- Bot creates an invoice for $128, sends a Stripe link.
- Customer taps link → pays with Apple Pay → Stripe fires a webhook to ZiFlow.
- Bot: "Payment received, thanks! Courier will deliver today before 6 pm."
- The CRM lead flips to
paid; the rep sees a new entry in "Ready to ship".
Step-by-step setup
Dashboard → Billing → Accept payments → Connect Stripe. Complete OAuth or paste API keys for a local processor. ZiFlow fires a $1 test charge (auto-refunded) to confirm.
Billing → Invoice types → Create. At least two: "One-time" and "Subscription". For subscriptions set the cadence (monthly, every 14 days) and first charge date.
Templates → Invoice. Example: "Your order: {items}. Total: {amount}. Pay here: {link}. Link expires in 48 hours." Variables are substituted automatically.
AI Agent → Scenarios → Payment → Auto-invoice → On. Trigger: "customer confirms order or books with deposit". Send Stripe link, Apple/Google Pay button, or both.
Billing → Webhooks → Copy URL. Format: https://ziflow.me/api/payment/webhook/{your_uid}. Paste into Stripe → Developers → Webhooks. HMAC signatures are verified automatically.
CRM → Settings → Automations → Add rule. "On successful payment → stage Paid + tag paid + write amount to lastPayment".
Settings → Notifications. Enable a channel (Telegram, Slack, email) for "New payment". Example: "Payment $128 from +1 512 555 0123, order #4821".
AI Agent → Scenarios → Payment → Retry. Reminders at 2, 24 and 48 hours. After the third — tag payment_abandoned and hand off for manual follow-up.
What good looks like
After a month, compare against baseline:
- Invoice → payment conversion: over 70% within the first 24 hours.
- Average order-to-payment time: under 5 minutes.
- Manual reconciliation count: 0. If a rep is still opening the bank dashboard, the webhook isn't wired correctly.
We used to lose 20% of orders at the "I'll Venmo you later" stage. A link in the chat closes the sale while the customer still wants the thing.
— Marcus Reid, online boutique owner, Austin
Common pitfalls
Keep reading
If you're collecting deposits for appointments, pair this with the auto-booking playbook. For verticals that live on deposits, see the beauty salon guide. Comparing with chat tools that have no payment module — ZiFlow vs Jivo.