hivein for Stripe
Ask about balances, charges and subscriptions in plain English; money-moving actions wait for confirmation.
hivein calls the Stripe REST API at api.stripe.com/v1, authenticating with a Stripe secret key sent as a bearer token, so a test key keeps every call in test mode.
- Reconcile the balance
- Trace a payment end to end
- Answer a billing question about one customer
- Drive an invoice through its states
- Refund, cancel and review disputes
Your Stripe, as actions the copilot can take.
Reconcile the balance
Read available and pending balance per currency, then walk the BalanceTransaction ledger behind it. Each entry carries gross amount, fee and net, so revenue answers are after Stripe's cut rather than before it.
Trace a payment end to end
Follow a PaymentIntent through to its Charge, its receipt URL and its balance transaction, or pull the Event log to see what Stripe recorded and when. Failed charges come back with the outcome and decline detail attached.
Answer a billing question about one customer
Search customers by email, name or metadata, then read their Subscriptions, their Invoices and the upcoming invoice preview. That is enough to explain what someone was charged, on which plan, and what is due next.
Drive an invoice through its states
Create a draft invoice for a customer, finalise it, email it, attempt payment or void it. These are five separate write actions rather than one blunt send, so you can stop at draft and look before anything reaches the customer.
Refund, cancel and review disputes
Issue a full or partial refund against a charge or PaymentIntent with a Stripe reason code, or cancel a subscription immediately or at period end. Both move money, so hivein confirms the exact amount and target before calling. Disputes are read-only here, listed with their status and evidence deadline.
It reads your Stripe data model, not a generic one.
The schema is read first, so a question that spans two of these is one question, not two lookups.
“How much of my Stripe balance has cleared and how much is still pending”
“Which subscriptions went past due this month and which customers do they belong to”
“Show me the failed charges from the last seven days with their decline reasons”
“Draft an invoice for this customer for the annual plan and send it once I confirm”
Writes to Stripe wait for you.
The same three guardrails hold on every template. They are attached to the action itself, so they hold on every path. Watch the replay →
- 01
The plan is held
A plan that writes to a real system stops before it starts. You see the goal, the risk and every step, then confirm or reject.
- 02
Each write asks first
A tool marked ask-first shows the exact call with its values. Confirm it, edit the values, or reject it. Nothing runs until you decide.
- 03
A rejection is an instruction
Pick a reason and add a line. The copilot re-plans with what you told it instead of guessing.
Stripe questions.
Can hivein actually issue refunds, or is it read-only?
It can issue them. Refunds, subscription cancellation and the invoice finalise, send, pay and void actions are all in the connector. Each is classified as a write, so hivein stops and shows you the charge, the amount and the reason before the call goes out.
Can I try it against test mode first?
Yes, and the key decides. A sk_test_ secret key points every read and write at your Stripe test data, so you can rehearse a refund or an invoice run there. Swapping in a live key changes nothing else about how the connector behaves.
How does it deal with amounts and currencies?
Stripe returns amounts in the smallest currency unit, so 4250 is £42.50, and hivein reads the currency field alongside every amount rather than assuming one. Multi-currency accounts get a balance entry per currency instead of a single blended figure.
Connect Stripe. Get a copilot this afternoon.
No card, no agent configuration, no prompt to write. Sign in and approve the actions it may take.