Skip to main content

Tamara

Tamara is a Buy Now, Pay Later (BNPL) payment solution that allows customers to split their purchases into interest-free installments. Amazon Payment Services supports Tamara integration for seamless payment processing across multiple markets in the Middle East.

We support Tamara in KSA and UAE. Ensure your merchant account is configured for the appropriate market before integration.

API Endpoints

https://sbcheckout.payfort.com/FortAPI/paymentPage

Request Format

  • Method: POST
  • Content-Type: application/x-www-form-urlencoded
  • Submission: HTML Form (Client-side HTTPS POST)

Request Parameters

Parameter
command   String Max: 20 Required

Transaction type to be executed. For Tamara payments, only PURCHASE is supported.
Values: PURCHASE
Example. PURCHASE
access_code   String Max: 20 Required

Merchant access code obtained from Amazon Payment Services dashboard under Integration Settings.
Example. zx0IPmPy5jp1vAz8Kpg7
merchant_identifier   String Max: 20 Required

Unique merchant identifier assigned by Amazon Payment Services during account setup.
Example. CycHZxVj
merchant_reference   String Max: 40 Required

Unique order reference that must be unique per merchant. Alphanumeric characters, hyphens, underscores, and periods allowed.
Example. XYZ9239-yu898
signature   String Max: 200 Required

SHA-256 hash signature for request authentication and integrity validation.
Example. 7cad05f0212ed933c9a5d5dffa31661acf2c827a
phone_number   String Max: 19 Required

Customer phone number in international format. Required for Tamara eligibility verification.
Example. 00962797219966
amount   Integer Max: 10 Required

Payment amount in smallest currency unit (e.g., halalas for SAR, fils for AED). Must be positive integer.
Example. 10000
currency   String Max: 3 Required

Three-letter ISO 4217 currency code. Tamara supports SAR and AED.
Values: SAR, AED
Example. AED
language   String Max: 2 Required

Checkout page and notification language. Supported values: en (English) or ar (Arabic).
Example. en
customer_email   String Max: 254 Required

Valid customer email address for payment notifications and receipt delivery.
Example. customer@domain.com
payment_option   String Max: 10 Required

Payment method specification for Tamara transactions.
Values: TAMARA
Example. TAMARA
order_description   String Max: 150 Required

Human-readable description of the order or service being paid for.
Example. iPhone 6-S
customer_name   String Max: 40 Optional

Full name of the customer making the payment.
Example. John Smith
customer_ip   String Max: 45 Optional

Customer's IP address for fraud prevention. Mandatory if fraud service is activated. Supports both IPv4 and IPv6 formats.
Example. 192.178.1.10
convenience_fee   Integer Max: 10 Optional

Additional convenience fee in smallest currency unit. Consider currency decimal points when sending the fee.
Example. 10000
settlement_reference   String Max: 22 Optional

Unique reference passed to acquiring bank for settlement file identification.
Example. XYZ9239-yu898
merchant_extra   String Max: 999 Optional

Custom data that will be returned in the response and webhook notifications.
Example. JohnSmith
merchant_extra1   String Max: 250 Optional

Additional custom field for merchant-specific data.
Example. JohnSmith
merchant_extra2   String Max: 250 Optional

Additional custom field for merchant-specific data.
Example. JohnSmith
merchant_extra3   String Max: 250 Optional

Additional custom field for merchant-specific data.
Example. JohnSmith
merchant_extra4   String Max: 250 Optional

Additional custom field for merchant-specific data.
Example. JohnSmith
merchant_extra5   String Max: 250 Optional

Additional custom field for merchant-specific data.
Example. JohnSmith
return_url   String Max: 400 Optional

Custom URL where customer will be redirected after payment completion.
Example. https://www.merchant.com/return
order_metadata   Object Optional

Airlines/Travel/Insurance Only: Structured metadata containing flight, insurance, and passenger details. Required only for travel and insurance transactions.
Example. {'flight_reservation_details':{'pnr':'TR9088999'}}

Multiply your transaction amount by the currency decimal code per ISO code 3 before sending the amount parameter. Example: For 500 SAR (2 decimal places per ISO code 3), multiply by 100 to send 50000 in your request.

The merchant_reference must be unique per transaction.

Check signature calculation section to learn how to calculate the signature.

Airlines, Travel & Insurance Metadata

For airlines, travel, and insurance merchants, include the order_metadata parameter with the following structure:

Parameter
flight_reservation_details   Object Required

Container object for all flight-related information.
Example. {'pnr':'TR9088999','itinerary':[...]}
pnr   String Optional

Passenger name record representing the trip booking number.
Example. TR9088999
itinerary   Array Optional

Array of flight segments containing departure and arrival details.
Example. {'departure_city':'Dubai','arrival_city':'Riyadh'}
departure_city   String Optional

City of departure for the flight segment.
Example. Dubai
departure_country   String Optional

Country of departure for the flight segment.
Example. UAE
arrival_city   String Optional

City of arrival for the flight segment.
Example. Riyadh
arrival_country   String Optional

Country of arrival for the flight segment.
Example. KSA
carrier   String Optional

Airline carrier name or code.
Example. Emirates
departure_date   String Optional

Departure date and time in ISO 8601 format.
Example. 2018-10-17T07:26:33Z
class   String Optional

Flight cabin class for the segment.
Example. Economy
refundable   Boolean Optional

Indicates if the ticket is eligible for refund.
Example. true

Response Parameters

Parameter
command   String Max: 20

Transaction type executed.
Values: PURCHASE
Example. PURCHASE
access_code   String Max: 20

Merchant access code used in the request.
Example. zx0IPmPy5jp1vAz8Kpg7
merchant_identifier   String Max: 20

Merchant identifier used in the request.
Example. CycHZxVj
merchant_reference   String Max: 40

Unique order reference from the request.
Example. XYZ9239-yu898
amount   Integer Max: 10

Transaction amount processed (includes convenience fee if applicable).
Example. 10000
currency   String Max: 3

Currency code used for the transaction.
Example. AED
language   String Max: 2

Language used for the checkout page.
Example. en
customer_email   String Max: 254

Customer email address used.
Example. customer@domain.com
signature   String Max: 200

Response signature for verification.
Example. 7cad05f0212ed933c9a5d5dffa31661acf2c827a
phone_number   String Max: 19

Customer phone number from the request.
Example. 00962797219966
customer_name   String Max: 40

Customer name from the request.
Example. John Smith
fort_id   Integer Max: 20

Unique transaction reference generated by Amazon Payment Services.
Example. 149295435400084008
payment_option   String Max: 10

Payment method used for the transaction.
Values: TAMARA
Example. TAMARA
eci   String Max: 16

E-commerce indicator for transaction type classification.
Values: ECOMMERCE
Example. ECOMMERCE
order_description   String Max: 150

Order description from the request.
Example. iPhone 6-S
customer_ip   String Max: 45

Customer IP address from the request.
Example. 192.178.1.10
settlement_reference   String Max: 22

Settlement reference from the request.
Example. XYZ9239-yu898
merchant_extra   String Max: 999

Custom data from the request.
Example. JohnSmith
merchant_extra1   String Max: 250

Additional custom field from the request.
Example. JohnSmith
merchant_extra2   String Max: 250

Additional custom field from the request.
Example. JohnSmith
merchant_extra3   String Max: 250

Additional custom field from the request.
Example. JohnSmith
merchant_extra4   String Max: 250

Additional custom field from the request.
Example. JohnSmith
merchant_extra5   String Max: 250

Additional custom field from the request.
Example. JohnSmith
return_url   String Max: 400

Return URL from the request.
Example. https://www.merchant.com
response_message   String Max: 150

Human-readable response description in requested language.
Example. Success
response_code   String Max: 5

Numeric response code indicating transaction result.
Example. 14000
status   String Max: 2

Two-digit status code indicating transaction state.
Example. 20

Every parameter sent by the merchant in the request will be returned in the response, including optional ones. The convenience_fee will not be returned separately; instead, the amount will include the sum of the order amount and convenience fee.

Response Codes

For a complete list of response codes and their descriptions, please refer to our Error Codes Documentation.

<form method="post" action="https://sbcheckout.payfort.com/FortAPI/paymentPage" id="tamara_form">
<!-- Required Transaction Parameters -->
<input type="hidden" name="signature" value="2c862f1eb45796d990f7c9ccb796aef06b6a83861742cc494f8be45650f880a8">
<input type="hidden" name="command" value="PURCHASE">
<input type="hidden" name="merchant_reference" value="tesrtfgdged2358">
<input type="hidden" name="amount" value="5000">
<input type="hidden" name="access_code" value="AWhDMzqUiHeYJXFiMgaX">
<input type="hidden" name="merchant_identifier" value="LbscwkFC">
<input type="hidden" name="currency" value="SAR">
<input type="hidden" name="language" value="en">

<!-- Tamara Specific Parameters -->
<input type="hidden" name="order_description" value="Premium Product">
<input type="hidden" name="payment_option" value="TAMARA">
<input type="hidden" name="phone_number" value="500000001">
<input type="hidden" name="customer_email" value="otp.success@tamara.ai">

<input type="submit" value="Pay with Tamara" id="submit_btn" name="submit_btn">
</form>
Sample Response
command=PURCHASE
access_code=AWhDMzqUiHeYJXFiMgaX
merchant_identifier=LbscwkFC
merchant_reference=tesrtfgdged2358
amount=5000
currency=SAR
language=en
response_code=14000
response_message=Success
status=20
fort_id=149295435400084008
payment_option=TAMARA
customer_email=otp.success@tamara.ai
phone_number=500000001
order_description=Premium Product
eci=ECOMMERCE
signature=7cad05f0212ed933c9a5d5dffa31661acf2c827a

Testing The Integration

Sandbox Testing

Use the sandbox environment for development and testing:

  • Sandbox URL: https://sbcheckout.payfort.com/FortAPI/paymentPage
  • Test Email: Use otp.success@tamara.ai for successful test transactions
  • Test Phone: Use 500000001 for successful test scenarios

Go-Live Process

When ready to move to production, follow our Go-Live checklist.

Was this page helpful?

Thanks for your feedback!