The Stripe integration puts your payment data next to the conversation. When a member opens a ticket with a Stripe ID, the matching payment, customer or subscription appears as a card on the ticket. Your team can look things up on demand with /stripe, and create an invoice or a checkout link for the customer right from the ticket — Clarify sends the pay link, tracks the status, and flips the card to Paid when Stripe confirms.
You connect with a Stripe sign-in; no secret key is ever pasted into Clarify. Integrations cost no feature token.
Connect your Stripe account
Sign in with Stripe — we never see your secret key.
The connection is created the moment you confirm in Stripe's window — the integration is active from then on, and the remaining wizard steps fill in its behaviour.
How should lookups work?
/stripe picker and are skipped on ticket creation.Result cards
| Placeholder | Becomes |
|---|---|
%id% | The Stripe ID |
%mode% | Live or test mode |
%status% | The object's status |
%amount% | Amount and currency, e.g. 49.00 EUR |
%created% | When it was created |
%customer% · %name% · %email% | The customer |
%description% | The payment's description |
%balance% · %delinquent% | Customer balance and delinquency |
%renews% · %cancels% | Subscription renewal and cancellation dates |
%dashboard_url% · %receipt_url% | Links to Stripe; a button whose link is unavailable is hidden |
Using it in a ticket
Automatic lookups
Enable one of the ready-made Stripe inputs in a category — Stripe Order ID, Payment Intent ID, Charge ID, Checkout Session ID, Customer ID, Customer Email, Subscription ID or Invoice ID (see Ticket inputs). When the member answers it, the matching card is posted with the ticket's opening message. An ID that cannot be found leaves a short notice instead.
/stripe
Any support member can run /stripe in your server. It opens a picker:
| Action | What happens |
|---|---|
| Look up payment | Enter a payment intent, charge, checkout session or invoice ID (pi_, ch_, cs_, in_) — the card is shown to you only. |
| Look up customer | By customer ID (cus_) or e-mail address. |
| Look up subscription | By subscription ID (sub_). |
| Create invoice | Inside a ticket: product, unit price, quantity and (optionally) the customer's e-mail. Clarify creates and finalises a Stripe invoice due in 30 days. |
| Create checkout | Inside a ticket: the same form, producing a hosted Stripe Checkout link for a one-off payment. |
Creating a payment posts a status card into the ticket's staff surface — Awaiting payment with Update status, View in Stripe and Cancel — and sends the customer a card with a Pay button and a Decline button. A ticket has one active payment at a time. When Stripe reports the payment, the card flips to Paid on its own; Update status re-checks by hand.
Frequently asked
No. You authorise Clarify's Stripe platform to act on your account; the only thing stored for your server is the connected account's ID and name. Revoke access in Stripe at any time.
Lookup cards are part of the ticket's opening message on your team's side. If message mirroring is off, that message lives in the customer's ticket, so the customer sees them too. Payment requests always reach the customer by design.
Yes — Decline voids the invoice (or expires the checkout) and tells your team on the status card.
Related
Integrations overview
Connect Stripe, PayPal, Tebex, Patreon, GitHub or a webhook to bring orders, memberships, issues and events to your tickets.
PayPal
Create PayPal payment links from a ticket, paid straight to your PayPal account — with automatic confirmation when you use a PayPal REST app, or plain PayPal.Me links without one.