ChatFrom
In development

Stripe

Your chatbot shows customers their subscriptions, cancels one at the end of the period they have paid for or undoes that, and sends them a link to Stripe's billing page. Setting it up takes about five minutes.

What your customers can do

  • See their subscriptions: each plan, its price, and when it renews or ends.
  • Cancel one. The chatbot says which plan ends and on which date, and asks them to confirm. It ends at the end of the period they have paid for; nothing is refunded and nothing more is charged.
  • Undo a cancellation before it takes effect.
  • Change their card or see their invoices on Stripe's own billing page, through a link the chatbot sends.

Refunds and plan changes stay with your team: the chatbot offers a hand-off, or the billing page.

How a customer proves who they are

Before the chatbot shows or changes anything, the customer gives the email address on their Stripe account, and the chatbot emails a 6-digit code to it, from your chatbot's name. They type the code into the chat, and only then does the chatbot act, for that address alone, in that conversation and for that person: in a Telegram group, what one member proved does not count for the others.

  • The code works for 10 minutes and allows 5 tries. Once it is right, the conversation stays verified for 60 minutes.
  • The chatbot answers the same whether or not an account uses the address, and a wrong code is answered the same too, so it never tells anyone who your customers are.
  • A conversation can ask for 3 codes an hour, an address can be sent 3, and your chatbot 30, so nobody can fill a stranger's inbox. Every request counts, so three requests naming an address, from anyone, pause codes for it until the hour is up.
  • Only a scrambled form of each code is stored, which no one can turn back into the code.

In Stripe

  1. Create a restricted key for ChatFrom. The Stripe card under Tools has a link that opens Stripe's form with the permissions already chosen, in live or test mode; otherwise go to API keys and press Create restricted key.
  2. It needs Customers: Read, Subscriptions: Write, Products: Read (which names the plans) and Customer portal: Write, and nothing else.
  3. For the billing link, save your customer portal settings once. To try it with test data, save them in test mode too.

A test key (rk_test_…) works on your test data only, so you can try everything before you use a live key.

In ChatFrom

  1. Open your chatbot and go to Tools. Under Connections, tap + on Stripe.
  2. Paste the key and press Connect Stripe. ChatFrom checks it with Stripe, shows your account, and switches Subscription tools on when the key may read customers and subscriptions; if it may not, the card says which permission is missing and the tools stay off until you add it in Stripe and press Update key. The card also says when Products: Read is missing. Whether the key may make billing links shows only when a customer asks for one.
  3. Try it in the Playground: ask "I'd like to cancel my subscription", give the email of a test customer, and type the code from the email.

A workflow can use the same tools in its Tool Call step, such as stripe_subscriptions.

What stays safe

  • Your key is stored encrypted and is never shown again, to you or anyone else.
  • A cancellation always waits for the end of the period already paid for, and can be undone until then.
  • The chatbot cannot refund, charge, or change a plan.

To stop, switch Subscription tools off, or press Disconnect to delete the stored key; then delete the key in Stripe too. What else a chatbot can connect to is on the Connections page.