Epaytools Orchestra API

Name: Orchestra 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.

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.

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 | sh

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 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

GET STARTED

Start building with Orchestra API

Explore with Jentic

View OpenAPI Document

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 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 Jentic?

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

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.

Time to first call

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.

Epaytools Orchestra API

Connect the Orchestra API to your agent

Capabilities

Start building with Orchestra API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs