TigerPayDevelopers API v1 tigerpay.app

Get started

TigerPay API

Take card payments in AED on your website or app. Your server creates a payment, the customer pays on a page hosted by TigerPay, and TigerPay tells you the result.

How a payment works#

  1. Your server

    Create a payment. Call POST /v1/payments with the amount and your own order reference. TigerPay replies with a payment object that has a checkout_url.

  2. Your server

    Send the customer to checkout_url. Redirect their browser. The page lives on pay.tigerpay.app.

  3. Customer

    Pays on the TigerPay page. They type their card details there, not on your site.

  4. TigerPay

    Sends you a webhook. TigerPay calls your webhook URL with payment.succeeded (or payment.failed, payment.cancelled). The customer is sent back to your success_url.

  5. Your server

    Mark the order paid. Check the webhook signature, then mark the order paid and ship it.

The webhook decides, not the redirect

After checkout the customer is sent to your success_url whatever the result. Landing on that page does not mean they paid. Mark an order paid only after you receive payment.succeeded, or after GET /v1/payments/{id} shows "status": "succeeded".

Card details never touch your servers#

Customers enter their card on TigerPay's secure payment page at pay.tigerpay.app. Your server only ever handles the payment id, the amount and your order reference. You never see, send or store a card number. You do not build a card form.

After a payment succeeds, the payment object can show the card brand, the last 4 digits and the issuing country. The full card number is never shared with you.

Key facts#

Base URLhttps://api.tigerpay.app/v1
FormatJSON over HTTPS. Send Content-Type: application/json on POST requests.
AuthenticationA secret key in the Authorization: Bearer header. See Authentication.
CurrencyAED only.
AmountsStrings with exactly two decimals, such as "340.00". The minimum is "2.00".
IDsPayments start with pay_, refunds with re_, disputes with dp_, webhook events with evt_.
DatesISO 8601 in UTC, such as 2026-10-20T10:00:00.000Z.
Test and liveEvery account has test keys and live keys. They never see each other's data. See Testing.

What v1 does not include#

  • Saved cards
  • Subscriptions and recurring payments
  • A payouts API
  • Currencies other than AED
  • A card form you can put on your own page