- Docs
- Guides
Stripe customer card & actions
Connect your own Stripe account and the inbox shows each customer’s subscriptions, invoices and payments next to the chat. Your teammates — and, if you allow it, the AI assistant — can send a billing-portal link, retry a failed invoice, pause or cancel a subscription, refund a payment or add a credit, with an ownership check on every change. It is included with Starter, Pro, Lifetime and Reseller accounts.
Before you use it with real customers: connect a test-mode restricted key first (rk_test_…), try every action you plan to use on Stripe’s test data, then replace it with a live key.
1. Create a restricted key in Stripe
- In the Stripe Dashboard open Developers → API keys → Create restricted key. Name it “TalkingDot”.
- Set exactly these permissions and leave everything else on None. Write includes Read.
| Permission (as Stripe names it) | Set to | Why |
|---|---|---|
| Core → Customers | Read | Find the customer by email; their balance. Required. |
| Billing → Subscriptions | Read | Plans, status and renewal dates on the card. |
| Billing → Invoices | Read | Recent and failed invoices with their payment links. |
| Core → Charges and Refunds | Read | Payments and what was already refunded. |
| Core → Payment Intents | Read | Refunds named by a payment (pi_…). |
| Core → Products | Read | Plan names on the card. |
| Billing → Prices | Read | Prices of the plans. |
| Billing → Subscriptions | Write (only if you use it) | Pause or resume, cancel at period end or undo it, cancel now. |
| Billing → Invoices | Write (only if you use it) | Retry an open invoice. |
| Core → Charges and Refunds | Write (only if you use it) | Refunds (full or part). |
| Core → Customers | Write (only if you use it) | Add a credit to the customer balance. |
| Billing → Customer Portal | Write (only if you use it) | Billing-portal links (update a card, manage the plan). |
| Checkout Sessions → Checkout Sessions | Write (only if you use it) | Payment links for an amount (also for payment requests in chat). |
A write permission you leave on None only switches that action off in practice: Stripe refuses it and we show Stripe’s message, which names the permission to add. If a permission name in your dashboard differs, Stripe’s error message says which one the request needs.
- In TalkingDot open Settings → Integrations → Stripe, paste the key and click Test connection, then Connect Stripe.
- The key is stored encrypted and never shown again — not in the dashboard, not in logs, not in error messages.
- Secret keys (
sk_…) are refused: they can do anything in your account. Publishable keys (pk_…) can’t read customers. - A key starting with
rk_test_shows a Test mode badge: it sees only Stripe’s test data, and links open Stripe’s test pages. - We call the Stripe API from our servers, pinned to API version
2026-10-28.endive.
2. The Stripe card in the inbox
When a conversation has an email, the Customer section shows a Stripe card (it is cached for 10 minutes; ↻ Look up again asks Stripe right away):
- The customer’s name and email, how long they have been a customer, their balance (credit or amount owed), and what they spent — the lifetime total, or the total of their last 25 payments when they have more.
- Subscriptions: plan, price, status (active, trial, past due, unpaid, canceled…), the renewal or cancel date, and whether payment collection is paused.
- Invoices: number, amount, status and due date, with a link to Stripe’s hosted invoice page. Failed and overdue invoices are highlighted.
- Payments: amount, date, what was already refunded, failed and disputed payments.
- A link to the customer in your Stripe dashboard.
How customers are found. By email, with Stripe’s customer list filter (GET /v1/customers?email=) — Stripe’s search is not available to businesses in India, so we don’t use it. Stripe’s filter is exact and case-sensitive: we look the email up in lowercase and, if nothing is found, with its first letter capitalised. A customer saved as PAT@EXAMPLE.COM in Stripe is not found — correct the email in Stripe. When several Stripe customers share an email, the card shows all of them.
Like the WHMCS and WordPress cards, a card matched by an email the visitor typed says so: check it is really them before you share or change anything.
3. The actions
| Action | What it does | By default |
|---|---|---|
| Stripe customer | Reads the card above (for the AI: subscriptions, invoices, payments and their ids). | Runs on its own |
| Invoice payment page | The hosted invoice page of one of the customer’s invoices, to send them. | Runs on its own |
| Billing portal link | A short-lived link to Stripe’s customer portal: update the card, or manage plan, invoices and details. Uses your portal settings in Stripe (Settings → Billing → Customer portal). The link is shown once to whoever made it and kept out of the log. | Runs on its own |
| Retry an invoice | Charges an open invoice to the saved payment method again (after a card update, say). A decline is reported with Stripe’s reason. | AI asks a teammate · all teammates |
| Pause / Resume a subscription | Pauses payment collection (Stripe’s pause_collection; new invoices are voided by default, or kept as drafts, or marked uncollectible), optionally resuming by itself after some days. The subscription stays active. Resume turns collection back on. | AI asks a teammate · all teammates |
| Cancel at period end / Undo a cancellation | The subscription ends when the paid period ends (it stays active until then) — or renews again. | AI asks a teammate · all teammates |
| Cancel now | Ends the subscription immediately. Stripe does not refund the unused time by itself; refund a payment if you promised one. The inbox asks “are you sure?” first. | Off: nobody, not even the AI, until you switch it on in Settings → AI → AI actions → Stripe (cancel at period end is the gentler choice) |
| Refund a payment | Full or partial, with a reason (requested by customer, duplicate, fraudulent) and a note kept in Stripe. The inbox asks “are you sure?” first. | AI asks a teammate · all teammates |
| Add a balance credit | A credit on the customer’s Stripe balance; it comes off their next invoices. | AI asks a teammate · all teammates |
| Payment link for an amount | A Stripe Checkout page for an amount the customer agreed to pay, valid up to 24 hours. To send a tracked “Pay” card in the chat instead, use Request payment in the inbox (Settings → Payments). | AI asks a teammate · all teammates |
Change who may run each one — the AI on its own, the AI after a teammate approves, or not at all; all teammates, admins only, or nobody — in Settings → AI → AI actions. When the AI asks, the conversation shows an Approve & run banner to the teammates who may run it. With test mode on — or with Test (no changes) in the inbox — an action does every check and tells you what would happen, without changing anything in Stripe.
4. Safety: whose account it touches
- Verified customers only. Anything about an account needs a verified conversation (signed in on your site, an email code, or a teammate’s check). The AI asks the customer to verify first. Teammates can read the card of an unverified contact, but changes there are refused — only a test run is possible.
- Ownership, checked live, on every change. The subscription, invoice, payment or customer an action names must belong to a Stripe customer whose email is the verified email. We read the object from Stripe before each change. Someone else’s id — or one that doesn’t exist — gets the same “doesn’t belong to this customer” answer, so nothing is revealed. The AI can’t act on another customer by passing their ids.
- Money is checked. A refund is at most what is left on the payment, in the payment’s currency (a different currency is refused); disputed payments are left to Stripe’s dispute flow. A credit is in the customer’s currency. Payments without a Stripe customer (a guest checkout) can’t be refunded from the chat — do those in Stripe.
- Never twice by accident. Every change we send carries a Stripe
Idempotency-Keymade from the action run, so a retry can’t repeat it. And the same money action on the same payment, subscription or customer (with the same amount) is refused for 10 minutes after it was made — a double click, two teammates, or the AI and a teammate — with a note saying who did it. - Everything is logged. Every action — done, refused or a test — is on the conversation’s timeline, in Settings → AI → AI actions → Activity and in the audit log, with who ran it and who approved it. The Stripe key and billing-portal links are never logged; refunds and credits carry a note in Stripe’s metadata saying they came from TalkingDot.
- Your plan. If the workspace moves to a plan without Stripe, the card and the actions stop at once (the saved key stays until you disconnect).
Payment requests in chat
The same Stripe account can take payments for requests you send in a conversation (Settings → Payments): customers pay on Stripe’s checkout page and the card in the chat turns Paid. To confirm payments instantly, add a webhook endpoint in Stripe with the URL shown in Settings → Integrations → Stripe and the events checkout.session.completed, checkout.session.async_payment_succeeded, checkout.session.async_payment_failed, checkout.session.expired, then paste its signing secret there. Without it, open requests are checked every few minutes. Stripe keeps a checkout page open for at most 24 hours.
Questions
Do you store my customers’ Stripe data? Only the card shown in the inbox, cached for a few minutes per contact so the inbox stays fast; disconnecting Stripe deletes it. Actions read Stripe live.
Can it charge a new card or create subscriptions? No. It never sees card numbers: card changes happen on Stripe’s billing portal, payments on Stripe’s checkout page.
Stripe Connect platforms? The key works on your own account. Connected accounts are not supported.