Stripe

Balance transactions are the ledger of everything that moved through the account, so your assistant can read the month rather than the dashboard's summary of it, then reconcile that against the payouts that landed in the bank and the charges and refunds behind them. Everything here is filterable by date range and paginated, so it can work through the whole period rather than the first page.

What you end up with. A month of gross charges, refunds, fees and net payouts that ties back to what hit the bank account, with the dates each payout covers.

Start with it bringing you the information and you deciding.

Never without. Have it state the pagination it used and the currency it grouped by. These endpoints are cursor paginated and multi-currency, and a total assembled from one page or one currency looks exactly like a complete one.

Built on: List Balance Transactions / List Payouts / List Charges / List Refunds

The assistant can list invoices filtered to the ones still open, read each one down to its line items, and tell you who it went to and what it was for. That produces a chase list with the amount, the customer and the age of each invoice, rather than a number you then have to go and decode.

What you end up with. A list of unpaid invoices with customer, amount, what the invoice covers, and how long it has been outstanding.

Start with it bringing you the information and you deciding.

Never without. Check the status filter it used before you send anything to anyone. Draft, open, uncollectible and void are different states in Stripe, and chasing a customer for a draft invoice they never received is the failure mode here.

Built on: List Invoices / Retrieve Invoice / Get Invoice Line Items / Retrieve customer

Stripe's search query language is available to the assistant, so it can find the payment by customer, amount or status, then read the payment intent and the underlying charge for the actual decline reason rather than the generic message the customer saw. It can also check what payment methods that customer has on file and whether one of them has expired.

What you end up with. The decline reason in Stripe's own words, the payment method it was attempted on, and whether a retry has any chance of working.

Start with it bringing you the information and you deciding.

Never without. Keep the decline detail out of what you send the customer. Card issuer decline codes are for your diagnosis, and repeating them back to a customer is both unhelpful and occasionally revealing about their bank.

Built on: Search payment intents / Retrieve payment intent / Retrieve Charge Details / List customer payment methods

A payment link is a hosted checkout page you can paste into an email or a message, and the assistant can create one end to end: find or create the product, set the price, and generate the link. It supports up to twenty line items. Nothing has to be built, and you can list your existing links to reuse one rather than making a fourth version of the same thing.

What you end up with. A working checkout URL for the exact amount, ready to send, with the product and price recorded in Stripe rather than typed into the link.

Start with it doing the work and checking with you.

Never without. Read the amount and the currency on the finished link before it goes out. Stripe amounts are in the smallest currency unit, so a decimal point in the wrong place is a factor of a hundred and the customer is the one who finds it.

Built on: Create Payment Link / Create a price / Create product / List payment links / Retrieve payment link

The assistant can create a draft invoice for a customer, add the line items for the work, and read the invoice back to check it. Draft is a real state in Stripe: nothing is sent and nothing is owed until the invoice is finalized, which is a separate step. That gap is the review window, and nothing reaches the customer until you finalize.

What you end up with. Draft invoices sitting in Stripe with the lines already filled in, waiting on your read before anything is finalized or sent.

Start with it doing the work and checking with you.

Never without. Keep finalizing as your step, not its step. Finalizing moves the invoice from draft to open and collectable and makes it immutable where Stripe requires that, and correcting a finalized invoice means voiding it and issuing another one in front of the customer.

Built on: Create an invoice / Add lines to invoice / Get Invoice Line Items / Retrieve Invoice / Finalize an invoice

The assistant can look up the charge, check what has already been refunded against it, and issue a full or partial refund by charge ID or payment intent ID. It can then read the refund back to confirm the amount and status. Stripe does not reverse a refund, so the check happens before, not after.

What you end up with. A refund issued for a confirmed amount against the right charge, with the refund record read back and the customer's remaining balance clear.

Start with it doing the work and checking with you.

Never without. State the exact amount and the exact charge ID yourself, and have it list existing refunds on that charge first. A refund cannot be undone, the money leaves immediately, and a duplicate partial refund against a charge that was already partly refunded is the easy mistake to make.

Built on: Retrieve Charge Details / List Charge Refunds / Create Refund / Retrieve a refund

It can list the open disputes on the account, open any one of them for the full detail including the evidence fields and the current status, and pull the charge and payment intent behind it so you have the order, the amount, and the customer in one place. Submitting your response is a write to the dispute's evidence, and it can also attach internal notes to the dispute for tracking. What it gives you is the checklist: which fields are still empty and what each one is asking for.

What you end up with. The open disputes with the deadline and the amount on each, and the evidence fields listed out so you know exactly what still has to be found.

Start with it doing the work and checking with you.

Never without. Read the evidence back before it submits, and keep Close Dispute out of the instruction entirely. Stripe describes closing a dispute as dismissing it and accepting the loss, and says the action is irreversible, so a dispute closed by mistake is money you have given up without arguing.

Built on: List Disputes / Retrieve Dispute Details / Retrieve Charge Details / Retrieve payment intent / Update Dispute

It can find the subscription from the customer or by searching, read what is on it and when the current period ends, and then cancel. The connector's cancel action ends the subscription immediately, and Stripe stops charging from that point, which is not the same as letting the paid period run out. Have it read the period end and the amount back to you first, because that is the number the conversation with the customer is actually about.

What you end up with. The subscription canceled on the customer you named, with what they were paying and when their period was due to end recorded before it happened.

Start with it doing the work and checking with you.

Never without. Approve the specific subscription ID, never a customer name, and confirm whether the customer expects to keep the rest of the period they paid for. Cancel customer subscription ends it immediately and there is no action on this connector that reinstates a canceled subscription, so putting it back means creating a new one and explaining the gap.

Built on: Retrieve customer / Search subscriptions / List customer subscriptions / Retrieve subscription / Cancel customer subscription