Tamara
Beta
Last updated: August 16, 2023
Accept payments using Tamara, a popular payment method in the United Arab Emirates (UAE), Saudi Arabia, and Kuwait.
Information
To start accepting Tamara payments, contact your Account Manager.
Model | Collecting/Gateway |
|---|---|
Payment flow | Redirect |
Payment method types |
|
One-step payment | |
Capture | |
Refund | |
Partial refund | |
Return | |
Recurring payment |
Tamara payments follow a two-step process:
- Request a payment.
- Redirect the customer to a Tamara's hosted payments page to complete the process.
Tamara offers two integration types — Buy Now Pay Later and Pay Now. However, you can also use the single checkout option, which means:
- you can have only one Tamara button on your checkout page
- the payment option selection is on Tamara’s hosted payments page
Using this integration type enables your customers to use Tamara’s Buy Now Pay Later products. The Buy Now Pay Later product is defined by the value passed in any product_type fields. If you want to have multiple payment options, you can add several buttons to the checkout page. The customer can then select the option they want before they’re redirected.
Using this integration type enables your customers to use Tamara’s Pay Now product. Like the Buy Now Pay Later products, the Pay Now product is also defined by the value passed in any product_type fields. If you want to have multiple payment options, you can add several buttons to the checkout page. For example, if you’re configured to use pay_in_full and pay_by_instalment_3, you would have two different buttons on your checkout page. The customer can then select the option they want before they’re redirected.
You can create multiple buttons on your checkout page for the customer to choose from, each of which is linked to a payment request with a defined product_type field. For example, let's say you want to include both the pay_now and pay_in_3 options. In this case, you would need to create two buttons, with two payment requests pointing to the different payment options.
To add these options to your checkout page, add whichever of the following values you need to the processing.product_type field of the payment request:
pay_in_fullpay_by_instalment_2pay_by_instalment_3pay_by_instalment_4pay_by_instalment_6
If you receive a 202 Accepted response, with the status field set to Pending, your request was successful. You now need to redirect your customer as described in the following example.
If you use this option, the customer will be redirected to Tamara's hosted payments page, with only one payment button available for them to select.
To enable this functionality, omit the processing.product_type field from the payment request.
If you receive a 202 Accepted response, with a status field set to Pending, your request was successful. You now need to redirect your customer as described in the following example.
Information
You will be notified of the customer's chosen payment option when the customer completes the payment.
For the full API specification, see the API reference.
post
https://api.checkout.com/payments
Redirect your customer to the redirect.href link in the response. This will enable the customer to authorize the payment before they are transferred to your predefined success or failure URL.
You can retrieve details about an existing Tamara payment with the following endpoints.
For the full API specification, see the API reference.
get
https://api.checkout.com/payments/{id}
Depending on the merchant integration type and the payment status, information about the product_type may not be available. It may also not be part of the GET response.
If the payment has a captured status, the payment response will display the product_type field, showing the payment option selected by the customer.
Tamara supports both partial and full refunds. You can refund a payment through the Dashboard or by using the Refund API.
For the full API specification, see the API reference.
post
https://api.checkout.com/payments/{id}/refunds
If the customer does not complete their payment, we will expire the payment and send a payment_expired webhook within 30 minutes. If the customer cancels their payment, we will send a payment_expired webhook.
Once a payment is created, it cannot be voided by the merchant. To void a payment in progress, wait for the payment_captured webhook, and then process a refund. Communicating this in advance to your end customer can help you avoid chargebacks.
When using Tamara, you may receive the following webhooks.
| Webhook | Description |
|---|---|
| Sent when a payment request has been accepted by the payment provider (Tamara) |
| Sent when the payment has been successfully captured |
| Sent when a payment request has been rejected |
| Sent when the payment has expired or was canceled by the customer (usually after 30 minutes) |
| Sent when a payment request has been successfully initiated and accepted by Checkout.com |
| Sent when a refund has been declined |
| Sent when the refund of the payment has been (fully or partially) accepted |
| Sent when the payment has been (fully or partially) refunded |
To start testing, contact your Account Manager or Integrations Engineer to activate Tamara payments in the sandbox environment.
- Create a Tamara transaction and select the redirect link in the response to Tamara’s website.
- Sign in to the account by filling up one of the test phone numbers you have been provided with.
- Confirm the one-time password (OTP) code — it should be pre-filled for you in the sandbox environment.
- Fill in the card details, using one of the test card details provided to you.
- Select Submit. You should then be redirected to your predefined success URL.