MyFatoorah Payment API
★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingbearer5 EndpointsREST
For Agents
Initiate, execute, and refund payments across MENA payment methods using a MyFatoorah bearer token, with sandbox and production environments.
Use for: I need to charge a customer's card via MyFatoorah, Send a payment link to a customer in Kuwait by SMS, Check whether a MyFatoorah invoice was paid, Issue a partial refund on a MyFatoorah transaction
Not supported: Does not handle subscription billing, payouts to external bank accounts, or in-person POS terminals — use for one-off MENA online payments and refunds only.
Jentic publishes the only available OpenAPI specification for MyFatoorah Payment API, keeping it validated and agent-ready. MyFatoorah is a payment gateway covering the Middle East and North Africa, supporting cards, KNET, mada, BENEFIT, and a range of regional wallets. The API enables initiating a payment session, executing direct card payments, sending payment links via email and SMS, polling payment status, and processing refunds. Both a sandbox host (apitest.myfatoorah.com) and a production host (api.myfatoorah.com) are available, authenticated with a bearer token in the Authorization header.
Install Jentic One Beta
Connect the MyFatoorah Payment API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MyFatoorah Payment API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with MyFatoorah Payment API.
Initiate a payment session and retrieve the available regional payment methods for the merchant account
Execute a direct charge against a chosen payment method ID and amount
Send a hosted payment link to a customer by email or SMS for asynchronous collection
Poll the status of a transaction by InvoiceId or payment reference to confirm settlement
Process full or partial refunds against a settled MyFatoorah invoice
Use Cases
Patterns agents use MyFatoorah Payment API for, with concrete tasks.
★ MENA E-Commerce Checkout
Accept online payments in MENA currencies including KWD, SAR, AED, BHD, OMR, and QAR through cards, KNET, mada, and BENEFIT. The integration calls /v2/InitiatePayment to surface available methods and /v2/ExecutePayment to capture funds. MyFatoorah handles 3D Secure and regional scheme routing so a single integration covers most Gulf payment rails.
Call POST /v2/InitiatePayment for a 25.000 KWD order, then call POST /v2/ExecutePayment with the chosen PaymentMethodId and customer card details to capture the charge.
Send Payment Link by SMS or Email
Collect payments asynchronously by sending a hosted MyFatoorah payment link via SMS or email. The integration calls /v2/SendPayment with customer contact details and the invoice value, and MyFatoorah delivers the link and a return URL for completion. This suits invoicing, deposits, and remote sales where the customer is not on a checkout page.
Call POST /v2/SendPayment with the customer's phone number, an InvoiceValue of 50 SAR, and a CallBackUrl, and return the generated payment link.
Refund Reconciliation Workflow
Issue full or partial refunds against MyFatoorah invoices when customers cancel or return goods. The integration calls /v2/MakeRefund with the InvoiceId and refund amount and writes the result back to the order management system. /v2/GetPaymentStatus is used to confirm the original transaction is in a refundable state before issuing.
Call POST /v2/GetPaymentStatus to confirm the invoice is paid, then call POST /v2/MakeRefund with the InvoiceId and the refund amount.
AI Agent Payment Assistant
An AI agent operating a MENA storefront takes a natural-language order, searches Jentic for MyFatoorah payment operations, loads the InitiatePayment and ExecutePayment schemas, and chains them into a single charge. Jentic isolates the bearer token so the agent never holds the secret. This compresses MyFatoorah onboarding from days of bearer auth and webhook plumbing to a single intent search.
Search Jentic for 'process a MyFatoorah payment', load POST /v2/InitiatePayment and POST /v2/ExecutePayment, and charge the customer 100.50 SAR via mada.
Key Endpoints
5 endpoints — jentic publishes the only available openapi specification for myfatoorah payment api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/v2/InitiatePayment
Initiate a payment session and list available methods
POST
/v2/ExecutePayment
Execute a direct charge against a payment method
POST
/v2/SendPayment
Send a hosted payment link by SMS or email
POST
/v2/GetPaymentStatus
Look up transaction status by InvoiceId
POST
/v2/MakeRefund
Process a full or partial refund
POST
/v2/InitiatePayment
Initiate a payment session and list available methods
POST
/v2/ExecutePayment
Execute a direct charge against a payment method
POST
/v2/SendPayment
Send a hosted payment link by SMS or email
POST
/v2/GetPaymentStatus
Look up transaction status by InvoiceId
POST
/v2/MakeRefund
Process a full or partial refund
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
MyFatoorah bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents call MyFatoorah operations through Jentic and the Authorization header is injected at execution time — the raw token never enters agent context.
Intent-based discovery
Agents search by intent (e.g., 'process a MyFatoorah payment') and Jentic returns matching operations such as POST /v2/InitiatePayment and POST /v2/ExecutePayment with their request schemas, so the agent can chain them without browsing docs.
Time to first call
Direct MyFatoorah integration: 2-3 days for bearer auth, environment switching, and refund/error handling. Through Jentic: under 1 hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Stripe handles global card processing alongside MyFatoorah's regional MENA coverage.
Use Stripe for international currencies and use MyFatoorah for KNET/mada/BENEFIT methods that Stripe does not natively support.
FAQs
Specific to using MyFatoorah Payment API through Jentic.
Why is there no official OpenAPI spec for MyFatoorah Payment API?
MyFatoorah does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MyFatoorah Payment API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the MyFatoorah Payment API use?
MyFatoorah uses HTTP bearer authentication — every request must include `Authorization: Bearer {Token}`. Through Jentic, the bearer token sits in the encrypted vault and is injected at execution time, so agent code and prompts never see the raw secret.
Can I send a payment link by SMS with the MyFatoorah Payment API?
Yes. Call POST /v2/SendPayment with the customer's phone number, an InvoiceValue, and a CallBackUrl. MyFatoorah generates a hosted payment URL and delivers it to the customer; the response includes the same link for your records.
How do I process a refund through Jentic?
Search Jentic for 'refund a MyFatoorah payment', load the POST /v2/MakeRefund schema, and execute it with the original InvoiceId and the refund amount. The agent can chain GET payment status before refunding to verify the original charge settled.
Does the MyFatoorah Payment API have a sandbox?
Yes. The spec defines two servers: apitest.myfatoorah.com for the sandbox and api.myfatoorah.com for production. Develop against the sandbox host, then swap the base URL when going live — all five endpoints behave the same in both environments.
What payment methods does MyFatoorah cover?
MyFatoorah routes to MENA-specific rails including KNET (Kuwait), mada (Saudi Arabia), BENEFIT (Bahrain), Visa, Mastercard, and Apple Pay. The exact list available to your account is returned by POST /v2/InitiatePayment based on the invoice currency and amount.
GET STARTED