payabl. Payment Gateway API
FinanceBankingSignature (SHA-1)9 EndpointsREST
For Agents
Authorize card payments, manage pre-authorization and capture flows, process refunds and reversals, initiate hosted payment pages, and create embedded payment widget sessions.
Use for: Process a card payment and capture funds immediately, Reserve funds on a card for later capture, Capture the full amount of a pre-authorized transaction, Partially capture a pre-authorized transaction with a specific amount
Not supported: Does not handle payment method provisioning, merchant account management, or settlement reporting. Use for transaction processing, hosted checkout, and Web SDK integration only.
Process payments through direct server-to-server integration with comprehensive transaction management. The payabl. Payment Gateway API supports card payments with authorization, pre-authorization, capture, refunds, reversals, and credit fund transfers, plus hosted payment pages and embedded Web SDK widgets. Designed for PCI Level-1 merchants and multi-PSP merchants who need full control over checkout flows with support for 300+ global and local payment methods.
Install Jentic One Beta
Connect the payabl. Payment Gateway API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the payabl. Payment Gateway 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpayabl.com%2Fpayabl" | sh2
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%2Fpayabl.com%2Fpayabl" | 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 payabl. Payment Gateway API.
Authorize and immediately capture card payments with full transaction details
Pre-authorize funds on a card and capture later with full or partial amounts
Refund captured transactions with amount and currency specification
Reverse or cancel previously authorized or captured transactions
Send credit fund transfers (payouts) to cards for disbursements
Create hosted payment page sessions with redirect URLs for customer checkout
Generate Web SDK session IDs for embedded payment widgets in merchant sites
Authenticate requests using SHA-1 signature calculation with merchant credentials
Use Cases
Patterns agents use payabl. Payment Gateway API for, with concrete tasks.
★ E-commerce Payment Processing
Process card payments for online stores with immediate authorization and capture. The API accepts card details, cardholder information, and customer metadata, returning transaction status and unique IDs for tracking. Supports hosted payment pages for PCI-DSS compliance without handling raw card data, plus embedded Web SDK widgets for customized checkout experiences within merchant sites.
Authorize a 100 EUR payment using the payment_authorize endpoint with card details, cardholder name, and customer email, then store the returned transaction ID for future reference
Hotel and Car Rental Pre-authorizations
Reserve funds on customer cards without immediate capture for services like hotel bookings or car rentals. Pre-authorize the estimated amount at booking time, then capture the actual amount after service completion. Supports partial capture for scenarios where final charges differ from initial estimates, such as mini-bar usage or fuel charges.
Pre-authorize 200 EUR on a card for a hotel booking, then after checkout capture 180 EUR for the room and 25 EUR for incidentals using partial capture
Refund and Dispute Management
Process full or partial refunds for returned merchandise, canceled services, or customer disputes. The refund endpoint requires the original transaction ID, amount, and currency. Reversals can cancel transactions before settlement. Both operations return immediate status confirmation and new transaction IDs for reconciliation and audit trails.
Refund 50 EUR from a completed transaction using the payment_refund endpoint with the original transaction ID and currency
Marketplace Payouts and Disbursements
Send credit fund transfers (CFT) to vendor or seller cards for marketplace earnings, rewards programs, or cashback disbursements. The API accepts destination card details, amount, currency, and cardholder information, enabling automated payout workflows. Useful for gig economy platforms, affiliate programs, and two-sided marketplaces that need to distribute funds to multiple recipients.
Send a 150 EUR credit fund transfer to a vendor's card using the payment_cft endpoint with destination card number, expiration, and cardholder name
AI Agent Payment Orchestration
Automate payment workflows through AI agents using Jentic for credential-isolated transaction processing. Agents can dynamically authorize payments, handle pre-authorization and capture flows for variable-amount services, process refunds based on business rules, and initiate hosted payment sessions for user checkout. Jentic handles signature generation and credential management, keeping merchant secrets out of agent context.
Use Jentic to search for 'authorize a card payment', load the payabl. payment_authorize schema, and execute a request to charge 75 EUR with customer details and email notification
Key Endpoints
9 endpoints — process payments through direct server-to-server integration with comprehensive transaction management.
METHOD
PATH
DESCRIPTION
POST
/pay/backoffice/payment_authorize
Authorize and charge a card
POST
/pay/backoffice/payment_preauthorize
Pre-authorize (reserve funds on card)
POST
/pay/backoffice/payment_capture
Capture a pre-authorized transaction
POST
/pay/backoffice/payment_refund
Refund a transaction
POST
/pay/backoffice/payment_reversal
Cancel or reverse a transaction
POST
/pay/backoffice/payment_cft
Credit fund transfer (payout)
POST
/pay/payment/init
Initiate a hosted payment page
POST
/pay/payment/get_payment_widget_session
Get a Web SDK session ID
POST
/pay/backoffice/payment_authorize
Authorize and charge a card
POST
/pay/backoffice/payment_preauthorize
Pre-authorize (reserve funds on card)
POST
/pay/backoffice/payment_capture
Capture a pre-authorized transaction
POST
/pay/backoffice/payment_refund
Refund a transaction
POST
/pay/backoffice/payment_reversal
Cancel or reverse a transaction
POST
/pay/backoffice/payment_cft
Credit fund transfer (payout)
POST
/pay/payment/init
Initiate a hosted payment page
POST
/pay/payment/get_payment_widget_session
Get a Web SDK session ID
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring payabl. by hand means computing its SHA-1 request signatures from your merchant id and secret and driving the authorize, capture, and refund flow yourself. Through Jentic you install once, import the payabl. Payment Gateway API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
payabl. carries the transaction targets in the request body, so scope your agent to the operations it needs, such as authorizing or capturing a payment. You choose the operations it may call, so refunds and reversals are not included unless you add them.
Credential isolation
Your payabl. merchant id and secret key are stored once, encrypted, by your own Jentic One instance and used to sign requests at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'process a card payment' or 'refund a transaction', and Jentic returns the matching payabl. operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe API
Stripe provides a comprehensive payment platform with similar transaction management, subscriptions, and global payment methods
Choose Stripe for extensive platform features including billing, subscriptions, and Connect for marketplace payouts. Use payabl. for unified payment and business account management with 300+ payment methods and consolidated transaction tracking.
FAQs
Specific to using payabl. Payment Gateway API through Jentic.
What authentication does the payabl. Payment Gateway API use?
The payabl. API uses SHA-1 signature-based authentication. You compute a signature from request parameters and your merchant secret key, then include it as a 'signature' parameter in the request body. Jentic stores merchant credentials encrypted in the vault and generates signatures server-side, so raw secret keys never appear in agent context. Get started with Jentic One, the self-hosted execution layer.
Can I process card payments programmatically with the payabl. API?
Yes. Use the POST /pay/backoffice/payment_authorize endpoint to authorize and immediately capture funds on a card. You provide merchant ID, amount, currency, payment method, card details, and cardholder information. The API returns transaction status, transaction ID, and error details if applicable. Through Jentic, agents search for 'authorize a card payment', load the schema, and execute the request without manual signature calculation.
What is the difference between authorize and pre-authorize?
The payment_authorize endpoint immediately captures funds when the card is authorized. The payment_preauthorize endpoint reserves funds on the card without capture, requiring a subsequent payment_capture or payment_partialcapture call to complete the transaction. Use pre-authorization for services where final amounts are determined later, like hotels or car rentals.
How do I create a hosted payment page with the payabl. API?
Use the POST /pay/payment/init endpoint with merchant ID, amount, currency, return URL, and signature. The API returns a redirect_url and transaction ID. Redirect customers to this URL to complete payment on a payabl.-hosted page. After payment, customers are returned to your specified return URL with transaction details.
Can I refund transactions through the payabl. API?
Yes. Use the POST /pay/backoffice/payment_refund endpoint with merchant ID, original transaction ID, refund amount, currency, and signature. The API processes the refund and returns confirmation with a new transaction ID for the refund operation. For cancellations before settlement, use the payment_reversal endpoint instead.
What is a credit fund transfer (CFT) in payabl.?
Credit fund transfer (POST /pay/backoffice/payment_cft) sends funds to a card for payouts, disbursements, or cashback. You provide merchant ID, amount, currency, destination card details, and cardholder information. This is used for marketplace vendor payments, affiliate commissions, or rewards programs where funds need to be sent to recipient cards.
How do AI agents use the payabl. API through Jentic?
Agents search Jentic for intents like 'process a card payment' or 'refund a transaction'. Jentic returns the relevant payabl. operations (e.g., payment_authorize, payment_refund) with their input schemas and signature requirements. The agent calls the operation via Jentic's execution layer, which handles signature generation and credential isolation. Integration time drops from days to under an hour. Get started with Jentic One, the self-hosted execution layer.
Can I limit what my agent is allowed to do with the payabl. Payment Gateway API?
Yes. Because you run Jentic One yourself, you decide which payabl. operations your agent may call, so you can grant only the ones it needs, such as payment_authorize and payment_capture, while leaving out payment_refund, payment_reversal, and payment_cft. The payabl. API carries the transaction targets in the request body, and your own rules govern which operations and credentials the agent can use, so refunds and payouts are unavailable to the agent unless you add them. Your merchant id and secret key stay with your Jentic One instance and are used to sign requests at execution time rather than being placed in the agent's context.
GET STARTED