01Booking and billing are two separate systems
A booking assistant reads a calendar and writes a slot. That is a small, well-defined job: the slot is free or it is not. A payment is different. Money moves, a card can be declined, a customer can ask for a refund or dispute the charge, and each of those needs a defined path and a person who owns it. The AUTOMATE plan, at 2,997 EUR a month, lists a website chatbot that qualifies and books, DM and email auto-responders, booking automation and a CRM. Payments are not on that list.
- On AUTOMATE the chatbot qualifies the enquiry and books a slot
- DM and email auto-responders cover the routine questions around the booking
- A payment adds failure paths: a declined card, a refund, a disputed charge
- Each of those needs an owner on your side, not a guess from the bot
02How a payment can sit next to a chatbot
The usual pattern is simple. The chatbot finishes the booking, then replies with a link. The customer opens it, lands on a page hosted by the payment provider and types the card there. Stripe's documentation describes Payment Links this way: a Stripe-hosted payment page you can share by email, on social media or on your website, and its comparison table lists PCI compliance handling as supported. Its security guide adds that integrations which send payment details straight to Stripe, without passing through your own servers, reduce your PCI obligations. So the chatbot never sees a card number. This is how such a flow is commonly built, not a feature in our plans.
- The chatbot sends a link, and the card is typed on the provider's page
- Stripe Payment Links can be shared by email, on social media or on a website
- The confirmation should come from the provider's own notification, not from the bot saying so
- None of this is a listed feature of the AUTOMATE plan
03Questions for a vendor who says the bot takes payments
Ask who holds the card data. If the answer is 'the chatbot', stop the conversation; the answer you want is the payment provider. Ask what happens on a declined card, who issues a refund and how. Ask where the confirmation comes from, because a confirmation that exists only in the chat can disagree with the bank statement. Then ask to see a test payment run end to end on your own phone. Our post on what to ask before buying an AI chatbot covers the rest of the list. If a vendor cannot answer these in plain words, the payment part is not ready.
- Who holds the card data: the provider, never the bot
- What happens on a declined card, and who tells the customer
- Who issues a refund, and where the customer sees it
- Where the confirmation comes from
- A test payment shown end to end on your phone
04Where PROOF48 is the wrong choice
If you need a cart, products and checkout, that is a store, not a chatbot feature. Stores cost 2,500 to 4,500 EUR and get their own timeline; they are not part of the 48 hour offer, and our post on whether a store can ship in 48 hours explains why. If you only need to collect one payment for one service, a payment link made in your payment provider's dashboard needs neither a chatbot nor an agency. And if most of your customers reach you on WhatsApp or by phone, AUTOMATE does not cover those channels; a standalone WhatsApp or voice assistant for a business that already has its own site is a custom build, priced on request. We have published no case study of an assistant that takes payment, so we have no result to show you.
- Cart, products and payment: a store, 2,500 to 4,500 EUR, with its own timeline
- One payment for one service: a payment link from your provider is enough
- WhatsApp or phone as your main channel: not in AUTOMATE, custom builds are priced on request
- No published case study of a chatbot that takes payment
Payment at checkout, not in the chat
Rotiseria Baba Novac, a rotisserie in Bucharest, takes payment through Stripe checkout on its own ordering site at rotiseria.ro. The case study lists a cart, pickup slot selection at checkout and a confirmation email on every order, sent through Resend. It lists no chatbot, so we do not offer it as an example of an AI taking payment. It shows how we have built payment so far: on a checkout page, with the confirmation sent afterwards. Noryse and SunVolt Club also use Stripe checkout. We publish no sales figures for any of them.
See the build: Rotiseria Baba NovacQuestions, answered
Can the chatbot take card details in the chat?
It should not. Card details belong on the payment provider's own page. Stripe's security guide says that integrations which send payment information straight to Stripe, without it passing through your servers, reduce your PCI obligations. The chatbot's job is to send the link.
Does the AUTOMATE plan include taking payments?
Not as a listed feature. It lists an AI website chatbot that qualifies and books, DM and email auto-responders, booking automation, a CRM, review management and two custom automations a month. Payment is not on the list. Ask us before you assume it either way.
Can a chatbot at least send a payment link?
Technically a link is only text in a reply, but PROOF48 lists no payment links in AUTOMATE or on its AI assistant page, so ask us before you plan on it. What needs care is what comes after: who confirms the payment, who handles a refund and what the customer is told if it fails.
Does this work on WhatsApp?
AUTOMATE does not cover WhatsApp or phone. A standalone WhatsApp or voice assistant for a business that already has its own site is a custom build, priced on request, and we have not published a case study of one taking payment.
Where PROOF48 fits
A chatbot can book the appointment and then point the customer to a payment page, where the provider, not the bot, takes the card. PROOF48's AUTOMATE plan, 2,997 EUR a month, lists a chatbot that qualifies and books and does not list taking payment. A cart and checkout is a store, 2,500 to 4,500 EUR, and it is not part of the 48 hour offer.
Cosmin Tiu · Founder, PROOF48
Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.