Integrations
Connect Stripe, PayPal, Tebex, Patreon, GitHub or a webhook to bring orders, memberships, issues and events to your tickets.

Integrations connect Clarify to the tools you already use to sell and support. Once connected, a member's order, subscription or membership appears right on the ticket when it opens, your team can look things up and act — refund, invoice, open an issue — from inside Discord, and your own systems can receive every ticket event. No tab-switching, no copy-pasting IDs.

Integrations are optional and cost no feature token. Clarify runs perfectly well without them — connect one when you want payment, membership or code context on your tickets.

What integrations do

Collect the detail on open

Enable the integration's ready-made input in a category — order ID, transaction ID, member ID — and the answer becomes a card on the ticket the moment it opens.

Look up and act from Discord

/stripe, /tebex, /patreon, /paypal and /issue give your team lookups, refunds, payment links and issues without leaving the ticket.

Push events out

The Webhook integration sends signed ticket events to your own endpoint.

The integrations

Stripe

Look up payments, customers and subscriptions; create invoices and checkout links. Connects with a Stripe sign-in.

PayPal

Create PayPal payment links with automatic confirmation. Bring your own REST app credentials, or use a PayPal.Me name.

Tebex

Look up payments and subscriptions, refund, pause or cancel, and create checkouts. Paste your Checkout API keys and set up the webhook.

Patreon

Show a member's Patreon membership, auto-detected from their linked Discord account. Connects with a Patreon sign-in.

GitHub

Open GitHub issues from a ticket with /issue, using your repositories' issue templates. Connects with the GitHub App or an access key.

Webhook

Send signed ticket events to your own HTTPS endpoint.

How you connect

Sign in with the provider (Stripe, Patreon, GitHub)

Click Connect, a popup opens on the provider, you authorise (or install the GitHub App), and the popup closes. The dashboard shows a Connected state with your account or campaign name. Stripe and Patreon are active from that moment; the remaining wizard steps set their behaviour. You never handle tokens yourself.

Paste keys (PayPal, Tebex, Webhook)

You create credentials in the provider's own panel and paste them into Clarify; the integration page walks you through where to find them. Once saved, Test connection checks the keys — and Tebex additionally needs its webhook registered in the Tebex panel.

Whichever style an integration uses, its dedicated page has the exact click-by-click steps. Start from the card above.

On the ticket

Stripe, Tebex and Patreon offer ready-made inputs you enable in a category's Setup Inputs. When a member answers one, the lookup runs as the ticket opens and the result is posted as a card with the opening message (the Look up when a ticket opens setting, on by default). Patreon can also find the member from their linked Discord account without any input.

Manual lookups with /stripe, /tebex and /patreon answer the supporter who asked, privately. Payment requests created with /stripe and /paypal and checkouts from /tebex post a status card for your team and a Pay card for the customer, and flip to Paid when the provider confirms.

Result cards

Lookup results are shown as cards — blueprints you can restyle, with %placeholder% tokens such as %amount% or %status% that fill with live data. If you don't design a card, Clarify uses a sensible default.

Cards and the %placeholder% tokens are explained in full on Cards & placeholders.

Your keys stay encrypted

Every API key and secret you paste is encrypted at rest and never sent back to your browser — when you edit an integration, the field reads leave blank to keep the current value. For sign-in connections, Clarify stores only what it needs (a connected account ID, encrypted tokens, an installation ID).

See Encryption for exactly what's protected and how.

Frequently asked

Want to pull data from a system that isn't listed here — your own shop, CRM or API? That's what data connectors are for.