Install Jentic One Beta

Connect the PayTabs API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PayTabs 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpaytabs.com%2Fpaytabs" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpaytabs.com%2Fpaytabs" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 PayTabs API.

Create hosted payment pages with customizable fields for MENA payment methods

Capture pre-authorized transactions with full or partial amounts

Process refunds for completed transactions with reference tracking

Void pending authorizations before settlement

Query transaction status and details by transaction reference

GET STARTED

Start building with PayTabs API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use PayTabs API for, with concrete tasks.

★ MENA E-Commerce Checkout

Accept online payments from customers across the Middle East and North Africa. PayTabs creates a hosted payment page supporting cards (Visa, Mastercard, mada, AMEX), Apple Pay, and local methods like SADAD and Fawry. The merchant sends a payment request via POST /request with amount, currency, and callback URL, then redirects the customer to complete payment. PayTabs handles 3D Secure authentication and returns the result to the configured callback.

Create a payment request for 500 SAR with cart description 'Order #1234', customer email buyer@example.com, and return URL https://shop.example.com/callback

Pre-Authorization and Capture

Hold funds on a customer's card at order time and capture when the goods ship. PayTabs supports authorize-then-capture flows where the initial request places a hold and a subsequent capture call collects the funds. This is common for hotel bookings, car rentals, and marketplaces that need to confirm availability before charging.

Submit an authorization-only payment request for 1200 AED, then capture 1000 AED against the returned transaction reference via POST /capture

Refund and Void Management

Issue refunds for completed transactions or void pending authorizations before settlement. PayTabs processes full and partial refunds via POST /refund and cancels pre-settlement holds via POST /void. Each operation returns a reference for reconciliation and triggers webhook notifications to the merchant's configured endpoint.

Issue a partial refund of 200 SAR against transaction reference TST2345678 via POST /refund and confirm the refund status

AI Agent Payment Operations via Jentic

AI agents use the PayTabs API through Jentic to process payments, check transaction statuses, and issue refunds for MENA merchants without handling raw server keys. Agents search by intent, receive typed schemas, and execute calls with Jentic managing credential isolation. This allows automated order management workflows across Saudi Arabia, UAE, and Egypt.

Search Jentic for 'query a PayTabs transaction status', load the schema for POST /query, and execute with the transaction reference to check payment completion

Key Endpoints

6 endpoints — paytabs api provides payment processing for merchants operating in the middle east and north africa region.

METHOD

PATH

DESCRIPTION

POST

/request

Create a payment page and initiate a transaction

POST

/capture

Capture a pre-authorized transaction

POST

/refund

Issue a refund for a completed transaction

POST

/void

Void a pending authorization

POST

/query

Query transaction status by reference

POST

/token

Manage tokenized card operations

POST

/request

Create a payment page and initiate a transaction

POST

/capture

Capture a pre-authorized transaction

POST

/refund

Issue a refund for a completed transaction

POST

/void

Void a pending authorization

POST

/query

Query transaction status by reference

POST

/token

Manage tokenized card operations

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the PayTabs API by hand means managing its server-key authorization header on the secure.paytabs.sa host and sequencing request, capture, and refund calls yourself. Through Jentic you install once, import PayTabs from the API Directory, store the server key once, and your agent calls it.

Permission scoping

PayTabs carries its payment and transaction details in the request body, so scope the agent by the operations it needs, such as query or capture. You choose that set, so operations like refund or void are not included unless you add them.

Credential isolation

Your PayTabs server key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'process a payment in Saudi Arabia' or 'query a transaction', and Jentic returns the matching PayTabs operation with its typed request and response schemas so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using PayTabs API through Jentic.

What authentication does the PayTabs API use?

The PayTabs API uses a server key passed in the Authorization header. The key format is a string starting with 'S' provided in your PayTabs merchant dashboard. Through Jentic, this server key is stored encrypted and agents never see the raw credential.

Can I process mada card payments with the PayTabs API?

Yes. PayTabs supports mada debit cards as a payment method for Saudi merchants. When creating a payment request via POST /request, mada appears as an available payment method alongside Visa, Mastercard, and Apple Pay for SAR-denominated transactions.

What are the rate limits for the PayTabs API?

PayTabs applies per-merchant rate limits based on your subscription tier. Standard accounts can process up to 100 API calls per minute across all endpoints. Contact PayTabs support for higher throughput requirements.

How do I check a transaction status through Jentic?

Search Jentic for 'query PayTabs transaction', load the schema for POST /query, and execute with the transaction reference in the request body. Jentic injects the server key automatically and returns the transaction status, amount, and payment method in a structured response.

Which countries does the PayTabs API support?

PayTabs serves merchants in Saudi Arabia, UAE, Egypt, Oman, Jordan, and other MENA markets. Each region has specific payment methods available. The base URL varies by region (secure.paytabs.sa for Saudi, secure.paytabs.com for global).

Does PayTabs support recurring payments?

Yes. PayTabs supports tokenized recurring payments via POST /token. After the initial payment, the card token can be used for subsequent charges without the customer re-entering card details, enabling subscription and installment models.

Can I limit what my agent is allowed to do with the PayTabs API?

Yes. Because you self-host Jentic One, your own rules decide which PayTabs operations and credentials the agent may use. You can grant read-only access such as POST /query to check transaction status while withholding money-moving calls, or allow POST /request and POST /capture without exposing POST /refund and POST /void. Only the operations you explicitly add are available to the agent, and your server key is injected at execution time rather than shared with it.

PayTabs API

Name: PayTabs API
Brand: PayTabs API
Availability: InStock

Official vendor OpenAPI document · agent-readyPaymentsPayment ProcessingapiKey6 EndpointsREST

For Agents

Process payments, capture authorized transactions, issue refunds, and manage tokenized cards for merchants across the MENA region.

Use for: I need to create a payment page for a Saudi customer, I want to capture an authorized transaction, Check whether a refund was processed successfully, Retrieve the details of a specific transaction

Not supported: Does not handle accounting, inventory management, or shipping - use for payment collection and transaction management only.

PayTabs API provides payment processing for merchants operating in the Middle East and North Africa region. It supports payment page creation, transaction capture, void, refund, and query operations across cards and local payment methods. The API handles tokenized recurring payments and serves merchants in Saudi Arabia, UAE, Egypt, Oman, Jordan, and other MENA markets with multi-currency settlement.

Jentic One on Github View OpenAPI Document

Connect the PayTabs API to your agent

Capabilities

Start building with PayTabs API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

PayTabs API