Stripe, without opening Stripe.
Draft the invoice in the thread. Anything that touches a customer's money asks first.
- Free to start
- No card
- Nothing sends or spends without you
- Your own account, not a shared login
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Stripe details, and Ray takes it from there.
@Ray how much did we refund last week?
@Ray refund the last charge for that customer.
@Ray send Northwind their outstanding invoice.
@Ray post yesterday's failed payments to #finance each morning.
What Ray can and cannot do in Stripe
Reading is free, because reading changes nothing. Writing stops for you, apart from the drafts named below. The rest is not on Ray’s list.
40 reads wired, 7 actions that wait for a human, and 5 that do not.
Runs on its own
What Ray reads in Stripe
- Charges, refunds, disputes, and the balance behind them
- Invoices, subscriptions, customers, and what they are paying for
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Finalize an invoice, which is the point it can be paid
- Send an invoice to a customer
- Create a payment link, with every line on the card
- Refund a payment, with the exact amount on the card
- Settle an invoice: pay it, write it off, or void it
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Pay out or transfer money anywhere
- Delete a customer or a subscription
- Read a customer's bank account, card, or tax ID
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Stripe actions Ray can take, each one stopping in the thread with the real content before it happens.
- Finalize invoice
- Send invoice
- Create payment link
- Create refund
- Pay invoice
- Mark invoice uncollectible
- Void invoice
Runs without asking
- Create a draft invoice
- Edit a draft invoice
- Add a line to a draft invoice
- Edit a line on a draft invoice
- Remove a line from a draft invoice
None of these sends anything or moves money. They set the work up, and the step that makes it real is on the list above.
Finalize invoice
Showing the exact change before it happens, down to the amount.
How Ray works with Stripe
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Stripe
One click, right where you asked. Ray posts a connect card, you authorise Stripe with your own account, and the work you asked for picks up where it left off.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in Stripe, and tell Dana it is being looked at.
Finalize invoice
- Waiting on
- your approval
Ray uses Stripe together with the rest of your tools.
One ask can read Stripe, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.
What does connecting Stripe to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Stripe and it can do the Stripe part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Every person on the team connects their own Stripe account, so Ray can only reach what that person can already reach, and the history in Stripe shows who actually asked.
Security and permissions
- You authorise Stripe on its own login screen. Your password never passes through Ray.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- Disconnect Stripe in a message, or uninstall Ray and every connection it held is revoked.
Stripe and Ray, answered
The questions teams ask before they connect Stripe. Every answer is how this integration is built rather than a promise about it.
More finance, billing & signatures integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Stripe.
Free to start, no credit card, and it asks before it acts.