Tamara
Tamara buy now, pay later (Saudi Arabia, UAE, Kuwait, Bahrain, Oman): look up orders by your order number or Tamara id with status, captured, refunded and settled amounts, check payment types and customer eligibility. Capture and refund are included, installed switched off.
7-day free trial · No credit card · EU-hosted
Ask Tamara anything
Try a real prompt against Tamara via AnythingMCP — Claude calls the tools, returns the answer. Press Enter on your own message to install on Cloud.
Install Tamara on CloudClaude is AI and can make mistakes. Please double-check responses.
Setup in 2 minutes
- 1Start a free trial on cloud.anythingmcp.com.
- 2Click Tamara in the connector store. Paste credentials when prompted.
- 3Mint an MCP API key and point your AI client at the generated MCP URL.
Guides for Tamara
Step-by-step setup for the most popular AI clients.
Setting up Tamara
From the connector definition itself: where to find the credentials, what they need to be allowed to do, and which API this adapter talks to.
Tamara
This connector uses the Tamara merchant API (buy now, pay later in Saudi Arabia, the UAE, Kuwait, Bahrain and Oman): order lookup by your order number or by Tamara order id, payment types and pre-checkout eligibility, and webhooks. Capture and refund are included but installed switched off.
Setup (2 minutes)
- Sign in to the Tamara Partners Portal and open API Token Management, or use the API token Tamara sent with your merchant account. Sandbox and production have different tokens.
- Paste the token into
TAMARA_API_TOKEN. It is sent asAuthorization: Bearer <token>. The notification token and the public key are not used here. TAMARA_API_URLishttps://api.tamara.cofor production orhttps://api-sandbox.tamara.cofor the sandbox; it must match the token.- Install and run
tamara_list_payment_typesto check the token.
Identifiers: order_reference_id is your own order number sent at checkout (e.g. the shop order number); order_id is the UUID Tamara issued. Most questions start from your order number: tamara_get_order_by_reference.
Workflow
- Order status:
tamara_get_order_by_reference(ortamara_get_orderwith the Tamara id). Status flow: new, approved, authorised, then partially_captured / fully_captured, and partially_refunded / fully_refunded; canceled, declined and expired are final.paid_amountis what the customer has paid so far;settlement_statusandsettlement_datesay whether Tamara has paid you out. - Transactions: captures, refunds and cancels are inside
transactionsof the order. - Before checkout:
tamara_list_payment_types(what the store offers),tamara_check_payment_options(what this customer can use for this amount),tamara_check_customer_eligibility(is the customer blocked). - Webhooks:
tamara_get_webhookwith the id from the registration.
Writes switched off: tamara_capture_order (captures an authorised order when it ships) and tamara_refund_order (refunds a captured order). Both move money; an admin turns them on deliberately. Before each call show the user the order, the amount and the currency and wait for a yes.
Amounts: objects {amount, currency}; SAR and AED with 2 decimals, BHD, KWD and OMR with 3. Times are UTC, ISO 8601.
Errors: 401 means a wrong token or a token for the other environment (sandbox vs production). 404 on an order means no order with that reference or id in this environment. 400 or 422 on capture or refund name the field Tamara rejected (e.g. an amount above what can be captured).
Limitations: Tamara has no endpoint to list or search orders; look orders up by reference or id. Creating checkout sessions, authorising and cancelling orders, the claims API (sandbox only at Tamara) and settlement reports are not part of this connector.
Your AI is two clicks away from Tamara.
Install the connector, paste your credentials, ask your AI a question. 7-day free trial, no credit card.