Payment receipts
Branded WhatsApp confirmation the moment payment_intent.succeeded fires. Customer name, amount, currency, plan name, hosted-receipt link — all auto-bound from the Stripe object.
Channels & Apps
AI & Automation
Integrations & App Store
Business Tools
Already have a LetsBot account? Login to Dashboard
UK Registered (Companies House #15477940)
LetsBot connects your Stripe account to the official WhatsApp Business API and delivers branded notifications for every payment, refund, invoice, and subscription event — all without writing a single line of code.
Free to install · No credit card required · Cancel anytime
How it works
From the first install click to your first delivered WhatsApp message — under sixty seconds, with zero code.
One-click install from inside your Stripe Dashboard. The app requests no data permissions there — every operation runs server-to-server through the Connect OAuth grant you authorize separately.
The moment you authorize Stripe, LetsBot seeds nine pre-built templates — payment succeeded and failed; subscription created, updated, canceled and trial ending; invoice created, paid and overdue. All editable.
Every Stripe event triggers a templated WhatsApp message through the official Meta-approved Business API. Customers see receipts, recovery prompts, and renewal reminders the moment they happen — open rates speak for themselves.
Capabilities
Six categories of automation, all built around the Stripe object model — not bolt-on hacks.
Branded WhatsApp confirmation the moment payment_intent.succeeded fires. Customer name, amount, currency, plan name, hosted-receipt link — all auto-bound from the Stripe object.
On charge.failed or invoice.payment_failed, automatically nudge customers with a friendly WhatsApp prompt and a one-click update-payment-method link. Recover revenue that would otherwise leak.
Customers know about refunds before they have to ask. Trigger on charge.refunded or charge.dispute.created with a transparent message that builds trust instead of confusion.
Trial-ending warnings, renewal confirmations, cancellation acknowledgments, plan-change updates, past-due reminders. Your entire customer.subscription.* stream pipes through.
Configure WhatsApp reminders that fire before or after seven Stripe events: abandoned checkouts, upcoming invoices, overdue invoices, failed payments, ending trials, cancellations, and refunds.
Drag-and-drop editor with auto-bound Stripe variables — {CUSTOMER_NAME}, {PLAN_AMOUNT}, {INVOICE_URL}, dozens more. Bilingual (Arabic + English) and Meta-approval ready.
9 templates seeded on day one
The moment you connect Stripe we provision nine WhatsApp templates pre-formatted to Meta's UTILITY category requirements — so they ship straight to approval without the usual review-loop friction.
| Template | When it is sent |
|---|---|
stripe_payment_succeeded Ready |
Sent when a payment is successfully captured |
stripe_payment_failed Ready |
Sent when a payment attempt fails |
stripe_subscription_created Ready |
Sent when a new subscription is created |
stripe_subscription_updated Ready |
Sent when a subscription plan changes |
stripe_subscription_canceled Ready |
Sent when a subscription is canceled |
stripe_subscription_trial_ending Ready |
Sent before a trial period ends |
stripe_invoice_created Ready |
Sent when a new invoice is issued |
stripe_invoice_paid Ready |
Sent when an invoice is paid |
stripe_invoice_overdue Ready |
Sent as a reminder for an overdue invoice |
Trust & security
The Stripe App surface itself requests no data permissions. Every other operation runs server-to-server through the Connect OAuth grant your merchant authorizes separately on letsbot.net.
The Stripe App inside your Stripe Dashboard requests no data permissions and reads no customer data there; it only shows whether your account is linked. Events run server-to-server through the Stripe Connect OAuth grant the merchant approves on letsbot.net.
Each merchant gets a dedicated database. No cross-tenant queries are possible at the application layer; multi-tenancy is enforced by stancl/tenancy with database-per-tenant separation.
Event records: 24 months. Message bodies: 90 days. Backups: 30 days. No data sold, no model training, no ad-network sharing.
Meta Business Partner for the WhatsApp Business API, with on-platform template approval. Stripe Marketplace publisher. UK-registered company (Companies House #15477940) with public director records.
Simple pricing
The Stripe integration is an addon you attach to any LetsBot plan. Pick the plan that matches your message volume, employees, and storage — your Stripe addon stays the same price across all of them.
Adds the 9 pre-built WhatsApp templates, all Stripe event triggers, and the reminder builder on top of any active LetsBot plan.
Stripe addon + Starter plan, free for 14 days. No credit card.
For small stores starting Stripe-driven WhatsApp comms.
For active stores ready to scale Stripe automations.
High-volume merchants with custom requirements.
Every plan includes one official WhatsApp Business number. All prices in USD, billed monthly or annually. VAT may apply based on your billing country.
FAQ
No. The Stripe App surface requests no data permissions. Every other capability — listening to charges, refunds, invoices, subscriptions — runs server-to-server through the Stripe Connect OAuth grant your merchants explicitly authorize on letsbot.net. We never move funds, take application fees, or initiate payouts on your behalf.
Under sixty seconds in most cases. Install LetsBot from the Stripe Marketplace, click "Connect with LetsBot," authorize once on letsbot.net, and the nine pre-built templates appear immediately. Trigger any test charge in Stripe Test mode and the corresponding WhatsApp message queues right away.
The default nine templates ship pre-formatted to Meta's UTILITY category requirements, which is the highest-approval category for transactional notifications. Most pass Meta's review on first submission. You can edit body, header, and footer in our visual editor; pushing edits back to Meta for approval is a one-click action.
LetsBot strictly follows Meta's opt-in and opt-out rules. Transactional UTILITY templates (receipts, refunds) can be sent to any customer who has provided their phone number to your business. Marketing-style messages require explicit opt-in. Customers can reply STOP at any time and we honor it across every channel.
We store the minimum necessary to deliver and audit messages: event metadata (Stripe event id, type, occurred_at) for 24 months, sent message bodies for 90 days, encrypted backups for 30 days. We never store payment-method details, full customer records, or fund-flow data. Full retention details live in our Privacy Policy.
Stripe Payments, Billing (subscriptions and invoices), Customers, and Checkout. As soon as a merchant authorizes the Connect OAuth grant we automatically subscribe to payment_intent.*, charge.*, invoice.*, customer.subscription.*, and checkout.session.* webhooks.
Yes. Every template ships with English and Arabic body variants out of the box, and the editor supports any language Meta recognizes. RTL languages render correctly inside WhatsApp without extra configuration.
Discover other LetsBot solutions to grow your business
Install LetsBot from the Stripe Marketplace in one click. No credit card. No code. 14 days free, then as little as $21/month.
LetsBot Ltd · UK Companies House #15477940 · Meta Business Partner · Verified Stripe Partner
Dig deeper
Choose what you allow. You can change this at any time from “Cookie settings” at the bottom of every page. Privacy Policy
Essential
Needed for the site to work and stay secure: session, form protection, language memory and bot checks.
Analytics
Help us understand how pages are used and improve them, through Microsoft Clarity, which records page interactions such as clicks and scrolling.
Marketing
Measure how well our ads work, through Google Ads, the Meta Pixel and ChatGPT ads by OpenAI, including what our servers send to Meta and OpenAI.