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.