The Tebex integration brings your store into the ticket. A member who hands you a transaction ID gets their payment shown as a card the moment the ticket opens; your team can look up payments and subscriptions with /tebex, refund a transaction, pause, reactivate or cancel a subscription, and create a hosted checkout the customer pays from a link. When Tebex reports the payment, the checkout card flips to Paid.
You connect with your store's Checkout API keys plus a webhook, all pasted once and stored encrypted. Integrations cost no feature token.
Connect your Tebex store
Keys from creator.tebex.io → Developers. Set the webhook up in this order: add the endpoint in Tebex using the URL shown on the Tebex page in your dashboard, paste its signing secret here and save — then run the endpoint validation in Tebex. Validation can only succeed once the secret is saved.
The Tebex page also shows your Webhook URL with a copy button — it is unique to your server — and a Test connection button that checks the project ID and private key against Tebex.
How should lookups work?
/tebex picker and are skipped on ticket creation.Info cards
| Placeholder | Becomes |
|---|---|
%txn_id% · %reference% · %ident% | Transaction ID, subscription reference, basket ident |
%status% | Payment or subscription status |
%amount% | Amount and currency |
%created% · %next_payment% | Creation date, next charge |
%customer% · %email% | The buyer |
%products% | The purchased packages |
%recurring_reference% · %interval% | Subscription details |
%checkout_url% · %dashboard_url% | Links; a button whose link is unavailable is hidden |
Using it in a ticket
Automatic lookups
Enable one of the ready-made Tebex inputs in a category — Tebex Transaction ID (tbx-…), Tebex Subscription Reference (tbx-r-…) or Tebex Basket ID (see Ticket inputs). The matching card is posted with the ticket's opening message; an ID that cannot be found leaves a short notice.
/tebex
Any support member can run /tebex in your server. It opens a picker:
| Action | What happens |
|---|---|
| Look up payment | Enter a transaction ID — the payment card is shown to you only. |
| Look up subscription | Enter a subscription reference. |
| Refund payment | Refund a completed transaction by its ID. |
| Pause subscription | Pause a subscription until a date (YYYY-MM-DD). |
| Reactivate subscription · Cancel subscription | Resume, or permanently cancel, a recurring payment. |
| Create checkout | Inside a ticket: product, unit price, quantity and (optionally) the customer's e-mail. Clarify creates a hosted Tebex checkout. |
Creating a checkout posts a Tebex Checkout status card for your team — Awaiting payment, with Update status and Pay — and sends the customer a card with the Pay link. A ticket has one active checkout at a time. When Tebex sends the payment.completed event to your webhook, the card flips to Paid.
Frequently asked
Tebex validates the endpoint by sending a signed request. Clarify can only answer it once your webhook signing secret is saved — add the endpoint in Tebex, paste and save the secret here, then validate.
Payment and subscription events. Clarify reacts to completed payments to mark checkouts as paid.
Lookup cards are part of the ticket's opening message on your team's side; with message mirroring off, the customer sees them too. Checkout requests always reach the customer.
Related
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.
Patreon
Connect your Patreon campaign so a customer's membership shows up on their ticket automatically — from their linked Discord account or their member ID.