October 5, 2026
Documented: result summary fields and attempt history
Payments Library results now carry a flat summary of the final outcome (selectedPaymentMethod, transactionAmount, transactionCurrency, transactionTimestamp, providerTransactionId, providerAuthorizationCode, providerAccountId) and an attempts list with one entry per processing attempt, fallbacks included. These fields arrive with the next Orchestra API release. See Result Handling.
Documentation updates
- Google Pay Setup: Orchestra uses Google’s Direct integration. Registration needs the Orchestra public encryption key and the full Attestation of Compliance, both available from support. See Google Pay Setup.
- Gateway requirements: added Payzone, SLIM CD and SumUp. See Gateway-Specific Requirements.
October 2, 2026
New guide: Booking Lifecycle
How rental and booking platforms place a hold at booking, keep a token that works with any gateway, and then capture, charge the balance, add extras, refund or release the hold. See Booking Lifecycle: Hold Now, Charge Later.Documented: cards already stored at a payment provider
What you can do with cards your payment provider already tokenized, and how to keep charging them withuserToken. See Cards Already Stored at a Payment Provider.
Documentation updates
- Quickstart: now starts with the portal’s one-click mock environment.
- Minor corrections and clarifications across the guides, including scheduled payment examples, troubleshooting entries, setup pages and gateway requirements, mock payment gateways and Bank Pay.
September 27, 2026
New guide: Serving Many Merchants
How platforms run payments for many merchants, each with its own payment provider: one Payment Gateway Account per merchant, created through the API, and named on each transaction. See Serving Many Merchants.Documentation updates
- Clarified: sandbox and live are separate accounts (Testing & Going Live), payment operations are synchronous with status codes that follow the gateway result, what an API key can access, and which stored cards work across gateways.
- Improved: the Quickstart examples, links to PCI Scope and Compliance, and a new “Who Orchestra Is For” section on the home page.
- Refreshed: the
llms.txtfiles for AI tools.
September 25, 2026
Documented: Self-serve failover on charge, authorize and Payments Library sessions
fallbackUpgs works on POST /PaymentGateway/charge, POST /PaymentGateway/authorize and Payments Library sessions, with no need to contact support. Orchestra tries your backup gateways in the order you list them. See Multi-Gateway Failover.
September 18, 2026
Documented: Scheduled payments
Payment contracts charge a stored card on a schedule, for example monthly or for a fixed number of payments, and can be paused, resumed or cancelled. Available in production since July 13, 2026. See Scheduled Payments and the Payment Contracts API. The OpenAPI specification was refreshed at the same time.Documented: Country Lookup
GET /Tools/country returns the ISO country code of the card’s issuing country from its BIN. See Country Lookup.
Documented: generateToken and decline reasons
Add generateToken: true to a charge or authorize request to receive a gateway token with the payment result, with no separate tokenize call. See Gateway Tokenization. Payment results also carry rejectReasonCode, a decline reason normalized across gateways. See Result Handling.
September 6, 2026
New page: Outbound IP Addresses
The IP addresses Orchestra uses to call your payment providers, for providers that require allowlisting. See Outbound IP Addresses.August 23, 2026
Documented: Bank Pay coverage
The countries and currencies Bank Pay supports. See Bank Pay.August 19, 2026
Documented: Stored cards in Payments Library sessions
POST /EWalletOperations accepts an optional storedCards array (up to 3 previously tokenized cards). The CardPay entry form shows a “Pay by {brand} ****{last 4}” button per card, and the customer pays a saved card by entering only its CVV. Persist the non-sensitive card details from the tokenization result to build the array. See CardPay: Stored Cards.
February 16, 2026
New: Gateway failover with fallbackUpgs
POST /PaymentGateway/charge now accepts an optional fallbackUpgs array. If the primary gateway rejects the charge, Orchestra retries automatically through each gateway in the list in order, stopping at the first success.
February 4, 2026
New: eWallet Accounts can now be edited
eWallet Accounts (PayPal, BankPay, UPI, and CardPay credentials) can now be updated through the portal. Previously, the only way to change an account’s settings was to delete it and re-create it.January 23, 2026
New: Client Certificate support in eWallet sessions
POST /EWalletOperations now accepts an optional paymentGatewayCertName parameter. This allows Orchestra to authenticate with your payment gateway using a client certificate you’ve uploaded through the Orchestra Portal during the charge flow.
The parameter is supported at the root level and inside each entry of the fallbackUpgs array:
New: Mock gateways support 3DS flow
The built-in mock payment gateways now support the full 3-D Secure authentication flow. You can use them to test the CardPay 3DS scenario end-to-end in dev and QA environments without a live gateway connection.Fix: 400 error response schema corrected
The400 Bad Request response was incorrectly documented in the API spec as a single ValidationErrorMessage object. It now correctly reflects the actual response: an array of ValidationErrorMessage objects. No runtime behavior changed - this was a documentation-only correction.
Update: Developer portal URLs migrated to orchestrasolutions.com
Account activation and registration emails now link toorchestrasolutions.com. The previous epaytools.com domain is no longer used.