Paysend Enterprise API
★ Only Publicly Available OpenAPI DocumentPaymentsPayouts TransfersapiKey13 EndpointsREST
For Agents
Send international payouts to cards and bank accounts, retrieve FX rates, tokenize cards, and track transaction status across 100+ countries.
Use for: I need to send a payout to a bank account abroad, I want to transfer money to a card in another country, Get the current FX rate for a currency pair, Check the status of a pending payout
Not supported: Does not handle payment acceptance, invoicing, or subscription billing — use for outbound payouts, FX rates, and card-to-card transfers only.
Jentic publishes the only available OpenAPI specification for Paysend Enterprise API, keeping it validated and agent-ready. Paysend Enterprise API enables global payouts to cards and bank accounts across 100+ countries with real-time FX rate retrieval, bank validation, card tokenization, and transaction status tracking. The API provides 13 endpoints covering the full payout lifecycle from rate quotes through payment execution and balance management.
Install Jentic One Beta
Connect the Paysend Enterprise API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Paysend Enterprise 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 Paysend Enterprise API.
Send payouts directly to bank accounts in 100+ countries with local currency settlement
Transfer funds to Visa and Mastercard cards globally
Retrieve real-time foreign exchange rates for pay-to-card and pay-to-account corridors
Tokenize card details for secure recurring payout operations
Look up and validate bank details including SWIFT/BIC and routing information
Track payout task status from initiation through settlement
Query partner account balance for available funds verification
Use Cases
Patterns agents use Paysend Enterprise API for, with concrete tasks.
★ International Payroll Disbursement
Distribute salary payments to employees and contractors in 100+ countries via bank account transfers. Paysend handles currency conversion using real-time FX rates and local payment rail routing. The API allows bulk payout initiation with individual tracking IDs and status polling for each transfer until funds arrive.
Get an FX rate via POST /processing/fx.rateGet.p2a for USD to EUR, then execute a payout of $2000 to a European bank account via POST /processing/pay.toAccount
Card-Based Global Transfers
Send money directly to Visa and Mastercard cards worldwide. Paysend settles funds to the recipient's card in their local currency with competitive FX rates. Card tokenization enables repeat transfers without re-entering card details, and the card info endpoint validates card BIN data before transfer.
Tokenize a recipient card via POST /processing/card.createToken, get the FX rate via POST /processing/fx.rateGet, then send $500 to the card via POST /processing/pay.toCard
FX Rate Management and Quoting
Retrieve real-time foreign exchange rates for both card and bank account payout corridors before executing transfers. Separate rate endpoints exist for pay-to-card (fx.rateGet) and pay-to-account (fx.rateGet.p2a) corridors, reflecting different settlement costs. Rates can be used for customer-facing quotes before committing to a transfer.
Retrieve FX rates for GBP to INR via both POST /processing/fx.rateGet (card) and POST /processing/fx.rateGet.p2a (bank) to compare corridors
AI Agent Cross-Border Payment Orchestration
AI agents use the Paysend Enterprise API through Jentic to execute international payouts without managing API key rotation, FX rate selection, or bank validation logic. Jentic handles credential isolation and operation discovery across all 13 endpoints, enabling agents to send global transfers with a single intent query.
Search Jentic for 'send international payout', load the Paysend pay-to-account schema, and execute a transfer of 1000 GBP to a Nigerian bank account
Key Endpoints
13 endpoints — jentic publishes the only available openapi specification for paysend enterprise api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/processing/pay.toAccount
Send payout to a bank account
POST
/processing/pay.toCard
Send payout to a card
POST
/processing/fx.rateGet
Get FX rate for card transfers
POST
/processing/fx.rateGet.p2a
Get FX rate for bank transfers
POST
/processing/bank.get
Validate bank details
POST
/processing/bank.search
Search for banks by name
POST
/processing/card.createToken
Tokenize a card for payouts
GET
/processing/status/{taskId}
Check payout task status
POST
/processing/pay.toAccount
Send payout to a bank account
POST
/processing/pay.toCard
Send payout to a card
POST
/processing/fx.rateGet
Get FX rate for card transfers
POST
/processing/fx.rateGet.p2a
Get FX rate for bank transfers
POST
/processing/bank.get
Validate bank details
POST
/processing/bank.search
Search for banks by name
POST
/processing/card.createToken
Tokenize a card for payouts
GET
/processing/status/{taskId}
Check payout task status
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Paysend API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw API keys never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'send money to a bank account abroad') and Jentic returns matching Paysend operations with their input schemas including corridor-specific parameters, so the agent can execute the right transfer without navigating FX and validation steps manually.
Time to first call
Direct Paysend integration: 3-5 days for API key setup, FX flow implementation, bank validation, and testing across corridors. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Global payment platform with payout capabilities and broader feature set
Choose Stripe when you need both payment acceptance and payouts in a single platform, or when you need advanced features like marketplace splits and Connect accounts.
FAQs
Specific to using Paysend Enterprise API through Jentic.
Why is there no official OpenAPI spec for Paysend Enterprise API?
Paysend does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Paysend Enterprise 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 Paysend Enterprise API use?
The Paysend Enterprise API uses API key authentication sent in a request header with each call. Through Jentic, API keys are stored encrypted in the MAXsystem vault and agents receive scoped access without handling raw credentials.
Can I send money to both cards and bank accounts?
Yes. The API provides separate endpoints for each corridor: POST /processing/pay.toCard sends to Visa and Mastercard cards globally, and POST /processing/pay.toAccount sends to bank accounts. Each has its own FX rate endpoint (fx.rateGet for cards, fx.rateGet.p2a for bank accounts) reflecting different settlement costs.
How do I check a payout status through Jentic?
Use Jentic to search for 'check payout status', load the schema for GET /processing/status/{taskId} or POST /processing/task.statusGet, and execute with the task ID returned when you initiated the payout. The response shows the current state (pending, completed, failed) and settlement details.
Can I validate bank details before sending a transfer?
Yes. Use POST /processing/bank.get to validate specific bank details by code, or POST /processing/bank.search to look up banks by name. This confirms the bank exists and provides routing information before you commit to a transfer, reducing failed payout rates.
What is card tokenization used for in Paysend?
POST /processing/card.createToken converts card details into a secure token that can be reused for future payouts without re-submitting the full card number. This is used for recurring payout recipients (e.g., monthly contractor payments) and reduces PCI scope since raw card data does not need to be stored.
GET STARTED