Billing & payments
Payment status, without leaving the case.
Most billing questions resolve to one fact: what actually happened to this charge. Reading it directly removes the tab-switching that makes billing support slow.
What connects
A read connection to customers, charges, refunds and subscriptions for the account in question.
What crosses the boundary
- Received: charges, their status, refunds and disputes.
- Received: subscription state, plan and next billing date.
- Received: the last four digits and card brand only — never full card data.
- Sent: nothing. Refunds are raised as internal actions, not executed here.
What this lets you do
- Explain a charge a customer does not recognise, with the date and amount.
- Confirm whether a refund has actually been issued and when it should land.
- See a failed payment before the customer writes in about being locked out.
- Answer "why was I charged twice?" with the two specific charges.
Setting it up
- 1Connect with a restricted read-only key.
- 2Map customers between the two systems.
- 3Choose whether failed payments create proactive cases.
- 4Confirm nothing in the connection can write.
Permissions
Read-only, with a restricted key. Resolivo never requests write access and cannot issue refunds, cancel subscriptions or modify payment methods. Full card numbers are never available to it.
What you can ask once this is connected
- “Why was this customer charged twice?”
- “Has this refund been processed?”
- “Which customers had a failed payment this week?”
Where it stops
Strictly read-only. Every financial action remains a human decision executed in Stripe or through your finance process. This connection makes support faster; it does not give support the ability to move money.
Billing & payments
Others in this category.
Take better care of every customer.
Give your team the context, knowledge and AI they need to resolve problems properly — and know who needs attention before they ask.
Keep the mailbox you already use · The AI is never metered · [email protected]