Encoded's Gateway offers true Orchestration, a real-time payment decision layer.

Why is this useful? A gateway passes transactions on; orchestration decides where each payment should go.

  • One modern API can sit above multiple gateways and acquirers.
  • Routing decisions can use cost, card type, stored token, MCC, geography, risk and provider availability.
  • Open banking and fraud checks can add evidence for stronger authentication and liability-shift conversations.
  • Encoded Insights can support mid-contract acquiring negotiations and least-cost routing.
Traditional gatewayOne merchant relationship usually points at one gateway or acquiring route.
Merchant
Gateway
Encoded orchestrationA decision layer routes every transaction to the best available payment path.
Merchant
Many routes

Payment channels

Web checkout
Contact centre
IVR
Pay by Link
Recurring

Encoded Orchestration Layer

Real-time rules select the gateway, acquirer and security checks that fit the transaction.

Stored card or token
Least-cost acquiring
MCC and risk fit
Fraud signal
Open banking check
Provider status

Payment destinations

Gateway A
Gateway B
Acquirer A
Acquirer B
Open banking
Alt payments

Payment comes in, Encoded applies rules, and the transaction takes the best route.

Whose responsibility is it anyway?

Whose responsibility is it anyway?

The Payment Card Industry Data Security Standard (PCI DSS) was originally the brainchild of the world’s five largest payment card providers VISA, MasterCard, American Express, Discover and JCB International. Today, it is a global framework…

read more
Wise up on PCI DSS and Save a Fortune

Wise up on PCI DSS and Save a Fortune

Every contact centre that accepts credit and debit card payments over the telephone needs to be PCI DSS (Payment Card Industry Data Security Standard) compliant. However the process of becoming and staying compliant can be hugely expensive…

read more