Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Payments / Orchestra API
Orchestra API logo

Epaytools Orchestra API

55
AI ReadinessFoundational (C)55/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticPaymentsPayment ProcessingapiKey, bearer43 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Orchestrate card payments, 3-D Secure flows, network tokenisation, and refunds across multiple gateways. Authenticate with an X-API-Key header and a JWS bearer token.

Use for: Charge a card for 49.99 EUR through the configured gateway, Authorise a 200 USD payment and capture it after shipment, Refund a previous capture by transaction reference, Void a pending authorisation that hasn't been captured

Not supported: Does not handle accounting reconciliation, payouts to bank accounts, or fraud-scoring decisioning - use for card payment orchestration, 3-D Secure, and tokenisation only.

Jentic publishes the only available OpenAPI specification for the ePayTools Orchestra API, keeping it validated and agent-ready. Orchestra is a payment orchestration platform that brokers card operations, payment gateway charges, 3-D Secure sessions, network tokenisation, and PCI-conformant utilities across multiple acquirers. The API exposes 43 endpoints grouped under CardOperations, PaymentGateway, ThreeDsSessions, ThreeDsMerchants, NetworkToken, and CustomForms, allowing merchants to authorise, capture, refund, void, and tokenise payments while keeping card data out of their own environment. Authentication is dual: an X-API-Key header for tenant identification and a JWS bearer token for signed operations.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Orchestra API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Orchestra 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%2Fepaytools.com%2Fepaytools" | sh
2

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%2Fepaytools.com%2Fepaytools" | 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 Orchestra API.

Authorise, capture, refund, and void payment-gateway charges across configured acquirers

Issue 3-D Secure session tokens to drive cardholder authentication challenges

Tokenise card numbers via network tokenisation and delete tokens on demand

Validate cards and look up brand by BIN through the CardOperations endpoints

Manage payment gateway accounts and 3-D Secure merchant configuration via REST

Upload and version custom payment-form folders for hosted checkout experiences

Verify operation results through signed-data validation endpoints

Use Cases

Patterns agents use Orchestra API for, with concrete tasks.

★ Multi-Acquirer Payment Routing for an E-Commerce Platform

Merchants running cross-border checkout need a single API to route charges across multiple acquirers based on currency, BIN country, or reliability. Orchestra's PaymentGateway endpoints (charge, authorise, capture, refund, void) plus PaymentGatewayAccounts management let an agent select an account and execute the charge in one flow, keeping retry and fallback logic out of the storefront.

Call POST /PaymentGateway/charge with amount=49.99 EUR, the chosen gateway account name, and a tokenised card reference, then return the gateway response.

PCI-Scope Reduction via Hosted Card Operations

Merchants reducing PCI scope route card capture through Orchestra's CardOperations and CustomForms so card numbers never touch their servers. The /CardOperations token-then-validate-then-charge flow combined with hosted custom forms keeps the merchant out of SAQ-D scope while still supporting tokenisation and storage.

Call POST /CardOperations to obtain a session token, render the hosted form, then call POST /CardOperations/charge with the returned reference.

3-D Secure 2 Authentication for Strong Customer Authentication

European merchants under PSD2 must authenticate cardholders with 3-D Secure 2. Orchestra's ThreeDsSessions and ThreeDsMerchants endpoints provision the session token, register the merchant configuration, and return the challenge URL, so an agent can wire SCA into checkout without a direct directory-server integration.

Call POST /ThreeDsSessions with the cardholder details and amount, then return the challenge URL to the checkout page.

AI Agent Payments Tool via Jentic

An AI agent embedded in a back-office assistant can run refunds and lookups against Orchestra without holding raw API keys. Through Jentic the agent searches by intent (for example 'refund a payment'), loads the schema, and executes with the X-API-Key and JWS bearer scoped from the vault - a useful pattern when CSAT or finance bots need to act on transactions on behalf of staff.

Use Jentic search('refund a payment'), load the PUT /PaymentGateway/refund operation, and execute it with the original transaction reference and refund amount.

Key Endpoints

43 endpoints — jentic publishes the only available openapi specification for the epaytools orchestra api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/PaymentGateway/charge

Perform a payment-gateway charge

POST

/PaymentGateway/authorize

Authorise a payment-gateway charge

PUT

/PaymentGateway/capture

Capture a previously authorised payment

PUT

/PaymentGateway/refund

Refund a captured payment

DELETE

/PaymentGateway/void

Void a pending authorisation

POST

/CardOperations/charge

Charge through Orchestra-hosted card capture

POST

/ThreeDsSessions

Get a 3-D Secure session token

POST

/NetworkToken

Network-tokenise a card

POST

/PaymentGateway/charge

Perform a payment-gateway charge

POST

/PaymentGateway/authorize

Authorise a payment-gateway charge

PUT

/PaymentGateway/capture

Capture a previously authorised payment

PUT

/PaymentGateway/refund

Refund a captured payment

DELETE

/PaymentGateway/void

Void a pending authorisation

POST

/CardOperations/charge

Charge through Orchestra-hosted card capture

POST

/ThreeDsSessions

Get a 3-D Secure session token

POST

/NetworkToken

Network-tokenise a card

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

O

Orchestra API

- Foundational (C)
55/100
73
Foundational Compliance
63
Developer Experience & Jentic Compatibility
30
AI-Readiness & Agent Experience
94
Agent Usability
63
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
92%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

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

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

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

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

51%

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.

30

AI-Readiness & Agent Experience

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

Grade: FSignals: 4
65%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

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

54%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

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.

63

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
62%

Authentication Strength

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

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

Setup

Wiring Orchestra by hand means combining its API-key request header with a JWS bearer token, sequencing the authorize, capture, and refund calls yourself, and building your own retries against api.epaytools.com. Through Jentic you install once, import the Orchestra API from the API Directory, store the key and token once, and your agent calls it.

Permission scoping

Orchestra sends the card and payment details in the request body rather than the URL, so scope the agent to the operations it needs, such as POST /PaymentGateway/authorize or POST /ThreeDsSessions. You pick that allowed set, so a money-moving operation like PUT /PaymentGateway/refund or DELETE /PaymentGateway/void is only reachable if you include it.

Credential isolation

Your Orchestra API-key request header and JWS bearer token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'charge a card' or 'refund a payment', and Jentic returns the matching Orchestra 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.

Complementary

Escrow.com API

→

Escrow service for high-value or item-based transactions

Choose when funds need to be held until delivery or acceptance, rather than charged immediately on a card.

Complementary

Esendex Messaging API

→

SMS notifications for payment confirmations and 3DS step-up codes

Pair with Orchestra to text payment receipts or out-of-band authentication codes to cardholders.

Complementary

EODHD Financial Data API

→

Currency and market data - pairs with multi-currency payment routing

Use when an agent needs FX context to route a charge to the most favourable acquirer currency.

FAQs

Specific to using Orchestra API through Jentic.

Why is there no official OpenAPI spec for the ePayTools Orchestra API?

ePayTools publishes integration documentation but not a public OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Orchestra 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 ePayTools Orchestra API use?

Orchestra requires an X-API-Key header (apiKey scheme) and a JWS HTTP bearer token for signed operations. Through Jentic both are stored encrypted in your Jentic One instance and injected at execution time so raw keys never enter the agent's context.

Can I run a refund with the ePayTools Orchestra API?

Yes. PUT /PaymentGateway/refund refunds a captured payment when supplied with the original transaction reference and refund amount. The acquirer used is determined by the gateway account on the original charge.

What are the rate limits for the ePayTools Orchestra API?

ePayTools does not document hard rate limits in the spec; throughput is governed by the merchant tier and the downstream acquirer. Treat acquirer responses as the authoritative limit and back off on 429.

How do I tokenise a card through Jentic?

Search 'tokenise a card to a network token'. Jentic returns the POST /NetworkToken operation, you load its schema, and execute with the card number and reference. The X-API-Key and JWS bearer are injected from the vault.

Does the API support 3-D Secure 2 for PSD2 SCA?

Yes. POST /ThreeDsSessions issues a session token for a 3-D Secure 2 challenge, and POST /ThreeDsMerchants/{name} registers merchant directory entries used by the SCA flow.

Can I host a custom checkout form on Orchestra?

Yes. PUT /CustomForms/{name} uploads or replaces a custom form folder, and GET /CustomForms lists the forms currently configured on the tenant.

Can I limit what my agent is allowed to do with the ePayTools Orchestra API?

Yes. Because you run Jentic One yourself, you decide which Orchestra operations your agent can call, so you can grant read-and-authorise work like POST /PaymentGateway/authorize or POST /ThreeDsSessions while withholding money-moving calls. A refund via PUT /PaymentGateway/refund or a void via DELETE /PaymentGateway/void is only reachable if you include it in the allowed set. Your X-API-Key header and JWS bearer token are held encrypted by your own instance and injected at execution time, so the agent operates strictly within the operations and credentials you permit.

GET STARTED

Start building with Orchestra API

Explore with Jentic One
View OpenAPI Document