Skip to main content

​
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. 
{
  "paymentGatewayAccountName": "primary-gateway",
  "fallbackUpgs": [
    { "paymentGatewayAccountName": "backup-gateway-1" },
    { "paymentGatewayAccountName": "backup-gateway-2" }
  ],
  "amount": 49.99,
  "currency": "USD",
  "card": "cardToken"
}
No changes required if you don’t use failover. See the multi-gateway failover guide for details.

​
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 clientCertificate parameter. This allows Orchestra to authenticate with your payment gateway using a client certificate during the charge flow. The parameter is supported at the root level and inside each entry of the fallbackUpgs array: 
{
  "operation": "CHARGE",
  "paymentGatewayAccountId": "my-gateway",
  "clientCertificate": "base64-encoded-cert",
  "fallbackUpgs": [
    {
      "paymentGatewayAccountId": "backup-gateway",
      "clientCertificate": "base64-encoded-cert-2"
    }
  ]
}

​
New: Mock Credential Provider

A mock credential service is now available for testing environments. It returns card-like payment tokens without requiring real payment gateway credentials, making it easier to test the full integration flow before going live. See the mock PSPs guide for setup instructions.

​
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

The 400 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 to orchestrasolutions.com. The previous epaytools.com domain is no longer used.