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.

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%2Fpaysend.com%2Fpaysend" | 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%2Fpaysend.com%2Fpaysend" | 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 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

GET STARTED

Start building with Paysend Enterprise API

Explore with Jentic One

View OpenAPI Document

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?

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

Setup

Wiring the Paysend Enterprise API by hand means managing its Authorization API-key header, choosing the sandbox or production host, and sequencing FX rate quotes with corridor validation before a payout yourself. Through Jentic you install once, import Paysend from the API Directory, store the API key once, and your agent calls it.

Permission scoping

Paysend carries its payout and transfer details in the request body, so scope the agent by the operations it needs, such as fetching an FX rate or checking a task status. You choose that set, so money-moving operations like pay.toAccount or pay.toCard are not included unless you add them.

Credential isolation

Your Paysend 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 'send money to a bank account abroad' or 'get a P2A FX rate', and Jentic returns the matching Paysend operation with its input schema including corridor-specific parameters so the agent calls the right endpoint without browsing the reference docs.

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 with Jentic One, the self-hosted execution layer.

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 your Jentic One instance 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.

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

Yes. Because you self-host Jentic One, your own rules decide which Paysend operations and credentials the agent may use, so you can grant read-only calls like fetching an FX rate with POST /processing/fx.rateGet or checking a task with GET /processing/status/{taskId} while withholding everything else. Money-moving operations such as POST /processing/pay.toAccount and POST /processing/pay.toCard are only available to the agent if you choose to add them to that set. The API key stays encrypted in your own instance and is injected at execution time, so the agent never sees it.

Paysend Enterprise API

Name: Paysend Enterprise API
Brand: Paysend Enterprise API
Availability: InStock

AI ReadinessFoundational (C+)59/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticPaymentsPayouts TransfersapiKey13 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

15%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C-Signals: 1

52%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Paysend Enterprise API to your agent

Capabilities

Start building with Paysend Enterprise API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Paysend Enterprise API

Jentic AI Readiness Score

Paysend Enterprise API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness