Tikkets Jamaica

Appearance

Payment methods and troubleshooting ​

Paying for tickets should be painless. Here's what to expect at the payment step, and what to do if something doesn't go to plan.

What this guide covers ​

Pay for your order by card. The platform supports two card processors — a Stripe intent-based flow and a Powertranz 3-D Secure flow. Which one you see depends on the event/platform configuration.

What you'll need ​

A checkout order with tickets in it.

Where to go ​

The payment step at the end of checkout.

SCREENSHOT_REQUIRED: end-user/payments/card-form SCREENSHOT_REQUIRED: end-user/payments/3ds-challenge

Step by step ​

  1. Enter your card details on the payment step.
  2. If your bank requires it, complete the 3-D Secure challenge (a code or approval from your bank).
  3. Wait for the confirmation page — do not close the tab while the payment is confirming.

And then? ​

  • Success: you receive a confirmation and can access your tickets from the email/receipt (see Access your tickets).
  • Failure: your order remains unpaid; no tickets are issued, and no money leaves your account for a failed authorization.

Good to know (rules & limits) ​

  • Processing fees (percentage + flat) are set by the platform and shown before payment.
  • If you close the browser mid-3DS, use the order link from your email to resume and re-check status.

If something goes wrong ​

  • "Payment declined" — most often the bank; try another card or contact your bank. Your tickets are not held indefinitely; retry promptly.
  • Paid but no confirmation — wait a few minutes and reopen your order from the email link; the platform reconciles payment status in the background. If still missing, contact support with your order reference (TKT-…).
  • Double charged? Failed attempts don't charge; successful ones appear on the receipt. Contact support with the order reference before disputing.

How accurate is this? ​

Verified: both processor flows exist in staging source (Stripe intent/confirm/check-status; Powertranz initiate/callback/challenge). Which processor is active per event is configuration-dependent.