Tebex payment links

Send a one-click Tebex payment link inside a ticket, let the customer pay without leaving the conversation, and see when the payment is confirmed.

A payment link lets support collect a payment without sending the customer away: staff pick a Tebex package, a payment link card appears in the ticket conversation, and the customer pays it in one click. The card switches to Paid once Joely has confirmed the payment with Tebex.

  • Permission: Send Tebex payment links from tickets. Only the Admin role has it by default (the project owner always can); grant it to other roles from Roles & permissions. The same permission covers cancelling a link and checking its payment.
  • Plan: payment links are available on paid plans. When the project owner's plan no longer includes them, new links and new payments are refused, but payments already made keep being confirmed.
  • Ticket: a link can only be sent on an open ticket. A link sent before the ticket was resolved or closed stays payable until it expires.
  • Store: the store needs its public token (Headless API), or a self-hosted bridge. A discount additionally needs the store's private key (Checkout API). See Tebex keys & security.

Open Send payment link from the Tebex card of the ticket sidebar, then choose:

  • One package (quantity 1). Packages hidden from pickers cannot be sent.
  • An optional discount, as a percentage from 1 to 99. See the rules below.
  • An expiry: 1, 3, 7, 14 or 30 days (7 by default).

A ticket can hold up to 5 pending links at a time. The card shows the package's catalog price, excluding tax, as it was when the link was sent; with a discount, that price is struck through next to the discounted one. VAT and currency conversion are computed by Tebex at payment time, so the amount charged can differ.

If the customer has linked a Discord account and enabled DM notifications for your project, they receive a short Discord message with a button to the ticket (not when they are already viewing it).

What the customer does

  1. The ticket author clicks Pay on the card. Other people invited to the ticket see the card without the button.
  2. Tebex requires a Cfx.re login before any purchase: the customer is sent to the Cfx.re login, then back to the ticket.
  3. The secure Tebex checkout then opens right away over the ticket, on mobile too.
  4. Once paid, the card turns Paid for everyone viewing the ticket.

Discounts

  • Payment links only offer percentage discounts.
  • A discount above your project's discount limit is refused for team members. The project owner is not limited.
  • The discount only applies when the Cfx.re account used to log in is the ticket author's. With another account, or when the author has no Cfx.re account, the customer can still pay the regular price: a notice says so as the checkout opens, and staff see "Discount not applied" on the card.
  • The discount is applied when your store supports it. If Tebex refuses it, the link falls back to the regular price and staff see it on the card.

How "Paid" is confirmed

Joely never trusts the browser: a link turns Paid only after Joely has checked the payment with Tebex. The check runs when the customer finishes the checkout, when they come back to the ticket, when staff click Check payment, and automatically every few minutes. A customer who closes the checkout early is picked up by the automatic check, usually within 10 minutes, and within an hour for links whose checkout was opened more than a day ago.

Staff see the transaction ID and the amount actually paid on the card. Customers see the payment date.

Expiry and cancellation

  • A link expires at the end of its expiry period. An expired link can no longer be paid.
  • Staff can cancel a pending link from the card. Cancelling is not a refund: a payment that was already in progress on Tebex is still recorded, and the card flags it as paid after cancellation.
  • The card cannot be deleted from the conversation: cancel the link instead.

Self-hosted bridges

Stores connected through a self-hosted Tebex bridge need bridge 1.2.0 or later, which exposes the basket routes. Until the bridge is updated, the customer's Pay fails with a message asking them to contact your support team, nothing is charged, and your staff see a "Bridge update required" notification when they check the payment.