Payabli API
Official vendor OpenAPI document · agent-readyFinanceBankingAPI Key211 EndpointsREST
For Agents
Process card and ACH payments, manage subscriptions and recurring billing, execute payouts to vendors, create and send invoices, query transactions and settlements, and handle customer payment methods.
Use for: Process a credit card payment for a customer order, Authorize a card transaction and capture it later, Set up a monthly recurring subscription for a SaaS customer, Issue a payout to a contractor or vendor via ACH
Not supported: Handles payment processing, payouts, and billing infrastructure. Does not provide business banking, lending, or general financial management - use for embedded payment operations only.
Accept and disburse payments through a comprehensive payment infrastructure platform. Payabli enables software companies to embed payment capabilities including card and ACH processing, subscriptions, payouts, invoicing, and merchant onboarding. The API provides full-lifecycle payment operations from authorization to settlement, with support for customers, vendors, and recurring billing.
Install Jentic One Beta
Connect the Payabli API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Payabli 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%2Fpayabli.com%2Fpayabli" | 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%2Fpayabli.com%2Fpayabli" | 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 Payabli API.
Process card and ACH payments with authorize-and-capture or direct sale flows
Create and manage recurring subscription billing with flexible schedules
Execute payouts to vendors and contractors via ACH or card
Generate and send invoices with attached files and payment links
Store and tokenize customer payment methods securely
Query transactions, settlements, batches, and transfers across organizations
Void, refund, and reverse transactions with full or partial amounts
Manage merchant onboarding and paypoint configurations
Handle chargebacks and dispute workflows
Subscribe to webhook notifications for transaction lifecycle events
Export transaction and settlement data in multiple formats
Use Cases
Patterns agents use Payabli API for, with concrete tasks.
★ Embedded Payment Processing for SaaS Platforms
Enable payment acceptance within SaaS applications without building payment infrastructure. Payabli's API supports both card and ACH transactions with authorize-capture flows, allowing platforms to control when funds are captured. Includes tokenization for recurring charges and PCI-compliant payment method storage. Ideal for marketplace, vertical SaaS, and platform businesses monetizing through embedded payments.
Process a $99.99 payment using a tokenized card for customer ID 12345, then create a receipt and send it via email
Recurring Subscription Billing
Automate recurring billing for subscription-based businesses. Create subscriptions with flexible schedules (monthly, quarterly, annual), manage trial periods, and handle failed payment retries. The API supports subscription updates, cancellations, and proration. Query endpoints provide subscription status and billing history for customer support and analytics.
Create a monthly $49 subscription starting on the 1st of next month for customer ID 789, with automatic retry on payment failure
Vendor and Contractor Payouts
Disburse funds to vendors, contractors, or marketplace sellers through ACH or card payouts. Payabli's MoneyOut endpoints support authorize-and-capture workflows for payout control, bulk payout processing, and transaction tracking. Useful for gig economy platforms, marketplace settlements, affiliate payments, and supplier disbursements.
Authorize a $1,500 ACH payout to vendor ID 456, then capture it after confirming the work is complete
Invoice Management and Payment Collection
Generate professional invoices with line items, attached files, and embedded payment links. Send invoices via email directly from the API, track payment status, and automatically reconcile paid invoices with transaction records. Supports custom invoice numbering, due dates, and partial payments. Ideal for B2B billing and service businesses.
Create an invoice for $2,500 with line items for consulting services, attach a PDF contract, and send it to the customer email address
Transaction Reporting and Settlement Reconciliation
Query transaction history, settlements, batches, and transfers across organizations and paypoints. Export data in multiple formats for accounting systems and reconciliation. Real-time access to transaction details, settlement status, and batch processing information. Supports date range filtering, pagination, and organization-level reporting.
Query all settled transactions for the last 7 days, calculate the total settlement amount, and export the data as a CSV report
AI Agent Payment Automation with Jentic
Automate payment workflows through AI agents using Jentic's payment orchestration. Agents can dynamically process transactions, manage subscriptions, execute payouts, and handle refunds based on business logic and customer context. Jentic handles credential isolation, schema discovery, and API complexity, enabling natural-language payment operations.
Use Jentic to search for 'process a refund', load the Payabli refund schema, and execute a partial refund of $25 for transaction ID 98765
Key Endpoints
211 endpoints — accept and disburse payments through a comprehensive payment infrastructure platform.
METHOD
PATH
DESCRIPTION
POST
/v2/MoneyIn/getpaid
Process a payment transaction (authorize and capture)
POST
/v2/MoneyIn/authorize
Authorize a card transaction
POST
/v2/MoneyIn/capture/{transId}
Capture an authorized transaction
POST
/v2/MoneyIn/refund/{transId}
Refund a settled transaction
POST
/Subscription/add
Create a recurring billing subscription
POST
/MoneyOut/authorize
Authorize a payout to a vendor
POST
/Invoice/{entry}
Create an invoice
POST
/Customer/single/{entry}
Add a customer record
GET
/Query/transactions/{entry}
Get list of transactions for a paypoint
GET
/Query/settlements/{entry}
Get list of settled transactions
POST
/v2/MoneyIn/getpaid
Process a payment transaction (authorize and capture)
POST
/v2/MoneyIn/authorize
Authorize a card transaction
POST
/v2/MoneyIn/capture/{transId}
Capture an authorized transaction
POST
/v2/MoneyIn/refund/{transId}
Refund a settled transaction
POST
/Subscription/add
Create a recurring billing subscription
POST
/MoneyOut/authorize
Authorize a payout to a vendor
POST
/Invoice/{entry}
Create an invoice
POST
/Customer/single/{entry}
Add a customer record
GET
/Query/transactions/{entry}
Get list of transactions for a paypoint
GET
/Query/settlements/{entry}
Get list of settled transactions
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Payabli by hand means passing its API key in the requestToken header, choosing the right sandbox or production host, and mapping the correct call across more than two hundred endpoints yourself. Through Jentic you install once, import the Payabli API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Payabli puts the transaction id in the URL path (/v2/MoneyIn/capture/{transId}), so a rule can pin your agent to one transaction: it can capture or query that transaction and nothing else. You choose the operations it may call, so refunds and payouts are not included unless you add them.
Credential isolation
Your Payabli API 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 card payment' or 'create a subscription', and Jentic returns the matching Payabli 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 offers payment processing with extensive developer tools and global payment method support
Choose Stripe for maximum payment method diversity and international reach. Use Payabli for white-label embedded payment solutions with revenue-sharing models for SaaS platforms.
FAQs
Specific to using Payabli API through Jentic.
What authentication does the Payabli API use?
The Payabli API uses API key authentication via the 'requestToken' header. You include your API key in the requestToken header with each request. Payabli provides separate sandbox and production environments with distinct API keys. Jentic stores Payabli API keys encrypted in the credential vault and provides scoped access tokens to agents, so raw keys never appear in agent context. Get started with Jentic One, the self-hosted execution layer.
What types of payments does Payabli support?
Payabli supports both card payments (credit and debit) and ACH (bank transfer) transactions. Card payments support authorize-capture flows for delayed capture, while ACH supports direct debits. The API also handles tokenized payments for stored payment methods, recurring subscriptions, and payouts to vendors via ACH or card networks.
How do I process a payment transaction with the Payabli API?
Use the POST /v2/MoneyIn/getpaid endpoint to process a payment in a single step (authorize and capture). Provide customer payment details, transaction amount, and paypoint configuration. For more control, use POST /v2/MoneyIn/authorize to reserve funds, then POST /v2/MoneyIn/capture/{transId} to complete the transaction. Through Jentic, agents search for 'process a payment', load the schema, and execute the request without manual API documentation lookup.
Can I set up recurring billing with the Payabli API?
Yes. Use the POST /Subscription/add endpoint to create recurring subscriptions with flexible billing schedules (daily, weekly, monthly, quarterly, annual). Specify start date, billing amount, payment method, and retry logic for failed payments. Query subscription status with GET /Query/subscriptions/{entry} and manage lifecycle with update and delete operations.
How do I handle refunds and voids?
For settled transactions, use POST /v2/MoneyIn/refund/{transId} for full refunds or POST /v2/MoneyIn/refund/{transId}/{amount} for partial refunds. For unsettled transactions, use POST /v2/MoneyIn/void/{transId} to cancel before settlement. The v2 endpoints return unified response codes for consistent error handling and transaction status tracking.
What are paypoints in the Payabli API?
Paypoints are merchant configuration entities that represent payment acceptance locations or business units within an organization. Each paypoint has its own processing configuration, credentials, and transaction history. Use paypoint IDs (entry parameter) to scope queries and operations to specific merchant accounts or locations.
How do I send payouts to vendors?
Use the POST /MoneyOut/authorize endpoint to create a payout transaction, specifying the vendor payment details, amount, and method (ACH or card). Then use GET /MoneyOut/capture/{referenceId} to execute the payout. For bulk operations, use POST /MoneyOut/captureAll to process multiple payouts at once. Query payout status with GET /MoneyOut/details/{transId}.
What webhook events does Payabli support?
Payabli supports webhook notifications for transaction lifecycle events including authorizations, captures, settlements, refunds, voids, subscription renewals, and failed payments. Configure webhook endpoints through the notification endpoints to receive real-time event data for automation and alerting.
How do AI agents use the Payabli API through Jentic?
Agents search Jentic for intents like 'process a card payment' or 'create a subscription'. Jentic returns the relevant Payabli API operations (e.g., POST /v2/MoneyIn/getpaid) with their input schemas. The agent calls the operation via Jentic's execution layer, which handles authentication and request formatting. Integration time drops from days to minutes. Get started with Jentic One, the self-hosted execution layer.
Can I limit what my agent is allowed to do with the Payabli API?
Yes. Jentic One runs self-hosted, so your own rules decide which Payabli operations and credentials the agent may use. Because Payabli puts the transaction id in the URL path, such as /v2/MoneyIn/capture/{transId}, you can pin the agent to a single transaction and allow only capture or query calls on it. Refunds through /v2/MoneyIn/refund/{transId} and vendor payouts through /MoneyOut/authorize stay off limits unless you explicitly add them.
GET STARTED