Orchestra API

Name: Orchestra API API
Brand: ePayTools Orchestra API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment ProcessingapiKey, bearer43 EndpointsREST

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.

Quickstart

Get started with Orchestra API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"charge a card payment"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Orchestra API 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

GET STARTED

Start building with Orchestra API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Orchestra API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Orchestra API 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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The X-Api-Key and JWS bearer token are stored encrypted in the Jentic vault (MAXsystem). Agents call Orchestra with a scoped reference; raw secrets never appear in the model context or logs.

Intent-based discovery

Agents search by intent (for example 'charge a card' or 'refund a payment') and Jentic returns the matching Orchestra operation along with its parameter schema, so the agent picks the right endpoint without parsing the spec.

Time to first call

Direct Orchestra integration: 3-5 days for dual auth handling, 3DS flow wiring, and refund/void plumbing. Through Jentic: under 1 hour — search, load, execute.

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 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 at https://app.jentic.com/sign-up.

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 the MAXsystem vault 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.