Payment control layer
Payment Orchestration Platforms
A payment orchestration platform can connect checkout, token storage, routing, authentication, gateways, processors, and reporting. It does not automatically provide a merchant account or make a merchant eligible for any connected payment route. Compare the exact orchestration product, then verify each processor, acquirer, MID, payment method, and funds contract that sits behind it.
Last reviewed
13 company profiles
Reviewed payment orchestration products
Each listed product is recorded as software that performs orchestration or routing without handling client funds or settling transactions. The listing does not supply or activate a merchant account: confirm every connected processor, acquirer, MID, token arrangement and funds route separately.
Publishes a position on
ACI Worldwide
ACI Worldwide supplies payment software. The merchant-facing ACI Payments Orchestration Platform provides an acquirer-independent gateway, routing, alternative-payment-method connections, omni-tokenisation, fraud decisioning and consolidated payment data. ACI Acquiring is separate software that banks and merchant acquirers use to run their own acquiring operations. In both products ACI provides technology; the merchant or PSP contracts with its chosen acquirers and payment providers, and those parties provide any merchant account or MID, underwrite payment acceptance, hold funds and settle transactions.
Payment orchestration products
ACI Payments Orchestration Platform
- ACI merchant payments orchestration
Why this option is listed
The recorded role for ACI merchant payments orchestration is Payment orchestration provider. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Payment orchestration provider
- Account / MID
- Not included with this product
- Approval
- Separate approval from the merchant's PSP or acquirer
- Funds / settlement
- ACI Worldwide does not hold merchant funds or provide merchant settlement
- ACI merchant payments orchestration
Product categories
Gateways · Payment orchestration
BR-DGE
BR-DGE is payment-orchestration software operated by Comcarde Limited. Its modular products provide hosted and API integration, connections to payment providers, rules-based routing, central tokenisation, consolidated reporting and white-label orchestration. BR-DGE states that it is not a payment service provider and does not hold funds; the merchant or white-label client retains its contracts with connected PSPs and acquirers, which provide the merchant account, any MID, payment underwriting, financial processing, funds custody and settlement.
Payment orchestration products
BR-DGE Integrate and Connect
- BR-DGE Connect payment-ecosystem access
Why this option is listed
The recorded role for BR-DGE Connect payment-ecosystem access is Payment orchestration provider. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Payment orchestration provider
- Account / MID
- Not included with this product
- Approval
- Separate approval from the merchant's PSP or acquirer
- Funds / settlement
- BR-DGE does not hold merchant funds or provide merchant settlement
- BR-DGE Connect payment-ecosystem access
BR-DGE Optimise
- BR-DGE Optimise smart-routing technology
Why this option is listed
The recorded role for BR-DGE Optimise smart-routing technology is Payment orchestration provider. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Payment orchestration provider
- Account / MID
- Not included with this product
- Approval
- Separate approval from the merchant's PSP or acquirer
- Funds / settlement
- BR-DGE does not hold merchant funds or provide merchant settlement
- BR-DGE Optimise smart-routing technology
BR-DGE White Label
- BR-DGE white-label orchestration
Why this option is listed
The recorded role for BR-DGE white-label orchestration is Payment orchestration provider. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Payment orchestration provider
- Account / MID
- Not included with this product
- Approval
- Separate approval from the merchant's PSP or acquirer
- Funds / settlement
- BR-DGE does not hold merchant funds or provide merchant settlement
- BR-DGE white-label orchestration
Product categories
Gateways · Payment orchestration
BVNK
BVNK provides managed stablecoin payment acceptance and payouts, fiat Virtual Accounts, Embedded Wallets and the self-managed Layer1 payment-orchestration product. The applicable BVNK entity, licence, supported assets, payment rails, custody model and settlement route depend on the product, jurisdiction and agreement.
Payment orchestration products
Layer1
- Layer1
Why this option is listed
The recorded role for Layer1 is Self-managed payment orchestration. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Self-managed payment orchestration
- Account / MID
- Customer supplies licences, custody and liquidity
- Approval
- BVNK activates access to the orchestration platform
- Funds / settlement
- BVNK does not hold or settle customer funds
- Layer1
Product categories
Payment orchestration · Crypto payments
CellPoint Digital
CellPoint Digital provides payment-orchestration software and gateway integration for travel and hospitality businesses. One Source Orchestration connects a merchant's contracted PSPs and acquirers, applies routing and failover rules, and consolidates payment operations and reporting. Velocity supports API, hosted-page and iframe integrations. CellPoint Digital does not provide the merchant account, MID or direct acquiring for these products, hold merchant funds, or settle funds to the merchant; the connected PSP or acquirer controls underwriting, processing and settlement.
Payment orchestration products
One Source Orchestration
- One Source Orchestration technology
Why this option is listed
The recorded role for One Source Orchestration technology is Payment orchestration provider. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Payment orchestration provider
- Account / MID
- Not included with this product
- Approval
- Separate approval from the merchant's PSP or acquirer
- Funds / settlement
- CellPoint Digital does not hold merchant funds or provide merchant settlement
- One Source Orchestration technology
Product categories
Gateways · Payment orchestration
Corefy
Corefy is a payment-orchestration platform and payment hub that connects a merchant's own payment-provider and acquirer accounts through one integration. It provides gateway, checkout, routing, payout orchestration, reporting and reconciliation software; it does not provide financial services, hold client funds or supply the merchant account.
Payment orchestration products
Payment Hub
- Payment Hub
Why this option is listed
The recorded role for Payment Hub is Payment orchestration provider. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Payment orchestration provider
- Account / MID
- Not included with this product
- Approval
- Each selected payment provider controls its own account activation
- Funds / settlement
- Corefy does not hold merchant funds or provide merchant settlement
- Payment Hub
Product categories
Gateways · Payment orchestration
Ecommpay
Ecommpay combines direct card acquiring, a proprietary payment gateway, local and alternative payment methods, open-banking payments, orchestration, recurring billing and merchant-funded payouts. Ecommpay Limited is the disclosed UK contracting and regulated payment-services entity; the exact acquiring route, external payment-method provider, settlement terms and payout rail remain product- and agreement-specific.
Payment orchestration products
Ecommpay payment orchestration
- Ecommpay payment orchestration
Why this option is listed
The recorded role for Ecommpay payment orchestration is Payment orchestration provider. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Payment orchestration provider
- Account / MID
- Not included with this product
- Approval
- Separate approval from the merchant's PSP or acquirer
- Funds / settlement
- Ecommpay does not hold merchant funds or provide merchant settlement
- Ecommpay payment orchestration
Product categories
Merchant accounts & acquiring · Gateways
FreedomPay
FreedomPay provides an independent payment gateway and payment-orchestration platform for in-store, online, mobile and unattended commerce, including travel and hospitality. Its platform connects merchants to selected processors, acquirers, payment methods and commerce systems, while Merchant Centered Acquiring is a separate referral advisory service. FreedomPay does not provide direct acquiring, a merchant account or MID on these models and does not perform merchant underwriting or merchant settlement; the selected processor or acquirer controls those responsibilities under its own agreement.
Payment orchestration products
FreedomPay Commerce Platform
- Independent omnichannel gateway and orchestration
Why this option is listed
The recorded role for Independent omnichannel gateway and orchestration is Gateway. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Gateway
- Account / MID
- Not included with this product
- Approval
- Separate approval from the merchant's PSP or acquirer
- Funds / settlement
- FreedomPay does not hold merchant funds or provide merchant settlement
- Independent omnichannel gateway and orchestration
Product categories
Gateways · Payment orchestration
Gr4vy
Gr4vy, Inc. supplies single-tenant cloud payment-orchestration software. Its universal API, Embed and Secure Fields checkout components, Flow rules, card vault, PSP and network tokenization, 3-D Secure controls, external anti-fraud connections, reporting and settlement-report reconciliation sit between a merchant and the merchant's own payment providers. Gr4vy for Platforms adds a white-label, multi-merchant route with separate workflows, routing and provider connections for each underlying merchant. The merchant or platform keeps the direct account, contract, fees and credentials with each connected provider. Gr4vy does not supply the acquiring merchant account or MID, perform payment underwriting or direct acquiring, hold merchant funds, or settle funds to the merchant.
Payment orchestration products
Cloud payment orchestration platform
- Cloud payment orchestration platform
Why this option is listed
The recorded role for Cloud payment orchestration platform is Payment orchestration provider. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Payment orchestration provider
- Account / MID
- Not included with this product
- Approval
- Each selected payment provider controls its own account activation
- Funds / settlement
- Gr4vy does not hold merchant funds or provide merchant settlement
- Cloud payment orchestration platform
Gr4vy for Platforms
- White-label multi-merchant payment orchestration
Why this option is listed
The recorded role for White-label multi-merchant payment orchestration is Multi merchant payment orchestrator. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Multi merchant payment orchestrator
- Account / MID
- Not included with this product
- Approval
- Separate approval from each connected provider
- Funds / settlement
- Gr4vy does not hold merchant funds or provide merchant settlement
- White-label multi-merchant payment orchestration
Product categories
Payment orchestration · Platforms, wallets & payouts
Outpayce
Outpayce provides the travel-focused Xchange Payment Platform for payment orchestration, gateway connectivity, alternative payment methods, refund messaging, reporting and reconciliation. XPP routes requests and data to customer-selected acquirers, gateways, payment service providers and other third parties. Those connected providers retain the merchant account, any MID, merchant underwriting, financial processing, funds custody and settlement. Outpayce S.A.U. is a Spanish electronic money institution, but that status does not authorize XPP as a direct acquirer or provider of a merchant account or MID.
Payment orchestration products
Xchange Payment Platform
- Xchange Payment Platform technology
Why this option is listed
The recorded role for Xchange Payment Platform technology is Payment orchestration provider. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Payment orchestration provider
- Account / MID
- Not included with this product
- Approval
- Separate approval from the merchant's PSP or acquirer
- Funds / settlement
- Outpayce does not hold merchant funds or provide merchant settlement
- Xchange Payment Platform technology
Product categories
Gateways · Payment orchestration
Praxis Tech
B2B payment orchestration platform connecting merchants to third-party PSPs and acquirers through hosted and API-based payment flows. Praxis is not the payment processor or acquirer, does not provide a merchant account, and does not hold merchant funds or provide merchant settlement.
Payment orchestration products
Payment Orchestration Platform
- Payment Orchestration Platform
Why this option is listed
The recorded role for Payment Orchestration Platform is Payment orchestration provider. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Payment orchestration provider
- Account / MID
- Not included with this product
- Approval
- Separate approval from the merchant's PSP or acquirer
- Funds / settlement
- Praxis Tech does not hold merchant funds or provide merchant settlement
- Payment Orchestration Platform
Product categories
Gateways · Payment orchestration
Primer
Primer provides payment-orchestration software through Universal Checkout, the Payments API, a centralized payment-method vault, Workflows, 3-D Secure, fraud-provider integrations, payment reporting and reconciliation. Merchants connect payment and fraud providers under their own agreements. A connected processor, PSP or acquirer controls any required merchant-account approval, processing and settlement. A fraud provider supplies only the fraud service it is contracted for. Primer does not provide merchant accounts, process payments, hold merchant funds or settle payments.
Payment orchestration products
Unified Payments Infrastructure
- Unified Payments Infrastructure
Why this option is listed
The recorded role for Unified Payments Infrastructure is Payment orchestration provider. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Payment orchestration provider
- Account / MID
- Not included with this product
- Approval
- Each selected payment provider controls its own account activation
- Funds / settlement
- Primer does not hold merchant funds or provide merchant settlement
- Unified Payments Infrastructure
Product categories
Payment orchestration
Recurly
Recurly is subscription-management, recurring-billing and payment-orchestration technology. A merchant connects its own supported payment gateway and merchant bank account; the gateway, processor and acquirer authorize the payment, underwrite the merchant account, hold any reserve and settle funds to the merchant's bank. Recurly stores and routes payment data, manages plans, invoices, subscriptions, retries, dunning and reporting, but its terms state that Recurly is not a bank, does not hold merchant or customer money and is not responsible for transaction amounts. Reach can be connected separately as merchant of record; that makes Reach, not Recurly, the seller and funds-flow party for that route.
Payment orchestration products
Recurly Subscriptions
- Recurly subscription billing technology
Why this option is listed
The recorded role for Recurly subscription billing technology is Payment orchestration provider. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Payment orchestration provider
- Account / MID
- Not included with this product
- Approval
- Separate approval from the merchant's PSP or acquirer
- Funds / settlement
- Recurly does not hold merchant funds or provide merchant settlement
- Recurly subscription billing technology
Product categories
Payment orchestration
Spreedly
Spreedly provides payment orchestration and a portable payment vault. Merchants connect their own payment providers and credentials; Spreedly supplies the API, tokenization, routing, retries, 3-D Secure, fraud-service integrations and reporting. It does not provide the merchant account, acquiring or merchant settlement.
Payment orchestration products
Connect
- Connect
Why this option is listed
The recorded role for Connect is Payment orchestration provider. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Payment orchestration provider
- Account / MID
- Not included with this product
- Approval
- Each selected payment provider controls its own account activation
- Funds / settlement
- Spreedly does not hold merchant funds or provide merchant settlement
- Connect
Optimize
- Optimize
Why this option is listed
The recorded role for Optimize is Payment orchestration provider. The provider operates the orchestration or routing software without handling client funds or settlement; connected processor, acquirer and merchant-approval terms remain separate.
Role, account, approval and funds
- Role in this product
- Payment orchestration provider
- Account / MID
- Not included with this product
- Approval
- Separate approval from the connected PSP or acquirer
- Funds / settlement
- Spreedly does not hold merchant funds or provide merchant settlement
- Optimize
Product categories
Payment orchestration
Decision brief
Confirm every underlying route before automating traffic
Use this page when
One control layer will connect several gateways, processors, acquirers or payment methods and choose where transactions are sent.
Contract boundary
Separate checkout, vault, routing and reporting functions from the financial-provider contracts behind each connection.
Route eligibility
Require live credentials and written coverage for the merchant entity, MID, activity, country and currency on every intended route.
Failure policy
Set when the system retries, changes route or stops, and who resolves reversals, duplicates and unmatched settlement records.
Evidence for the route go-live
- Route register with merchant entity, MID, acquirer, currency and approved activity
- Token owner, processor portability, PCI DSS responsibility and termination export
- Test results for timeouts, duplicate requests, reversals and manual override
Separate the control layer from the financial providers
Start with a responsibility map for the selected product. Record who hosts checkout, stores credentials, selects a route, transmits the payment request, authenticates the customer, acquires the transaction, holds a reserve, and settles funds. One orchestration contract may cover only the first parts of that chain.
A connector shown in a dashboard is not proof that the merchant has an active processor account, an approved MID, or commercial terms for that route. Ask whether the provider supplies a technical connection, manages a sub-account, refers the merchant, or contracts for any financial service in its own name.
- Orchestration contracting entity and product edition
- Connected gateway, processor, acquirer, and payment-method entities
- Merchant account or MID owner for every live route
- Entity that receives and settles customer funds
Build an activation matrix before designing routing rules
List every intended route by merchant legal entity, website or app, country, currency, payment method, processor account, and approved business activity. A routing rule should only send a transaction to a route whose agreement covers that transaction. Technical availability and commercial activation are separate states.
Ask what work the orchestration provider performs during activation and what remains with each connected provider. Certification, credentials, 3-D Secure configuration, descriptors, webhooks, fraud rules, and production testing can differ by connector and may need separate approval or implementation work.
Use route-level status
Track contracted, technically connected, certified, approved for the intended activity, and live as separate fields. One green connection indicator should not collapse those decisions.
Define token ownership, portability, and PCI responsibility
Confirm where raw account data enters the system, which entity stores it, whether the orchestration token can be used with more than one processor, and how network tokens or processor-specific tokens are mapped. A portable vault can reduce migration work only when the contract, token format, destination provider, and payment-brand rules permit the transfer.
Outsourcing payment processing does not remove every PCI DSS responsibility. The merchant should obtain the provider's current compliance evidence for the services used, document shared responsibilities, and confirm the validation method with its acquirer or other compliance-accepting entity.
- Hosted page, iframe, embedded fields, or direct API data path
- Vault owner and token portability by connector
- Current PCI DSS responsibility matrix and evidence
- Deletion, export, and migration procedure at termination
Test routing with real failure states, not a success-only demo
Define which signals can change a route and which must not. Country, currency, amount, card type, cost, processor health, and merchant entity can be useful inputs, but the rule set must preserve the account's approved scope. A soft decline, hard decline, timeout, duplicate request, and processor outage require different handling.
Ask how idempotency, authorization reversals, retries, cascades, circuit breakers, and webhook replays work. Repeating an authorization across processors can create duplicate holds or conflict with network and acquiring rules. The merchant needs an auditable reason for every route decision and a safe manual override.
Compare normalized operations and the exit path
A useful orchestration layer preserves both a normalized status and the underlying provider response. Finance and support teams need stable transaction identifiers across authorization, capture, refund, dispute, fee, and settlement records. Confirm export formats, data retention, webhook delivery history, role-based access, and incident escalation.
Before signing, request the procedure for exporting routing rules, connector configuration, tokens or token mappings, transaction history, and audit logs. Confirm which functions stop immediately at termination, which data remains available, and how the merchant can keep processing while a replacement is implemented.
FAQ
Common questions
Does an orchestration platform approve merchant accounts?
Not by default. An orchestration software product can connect approved routes without underwriting the merchant or providing the MID. Confirm the approval authority and contract for every connected financial provider.
Does a connector mean the payment method is ready to use?
No. The connector may exist while the merchant still needs a provider contract, credentials, certification, risk approval, country access, or production configuration for the exact route.
Can orchestration reduce PCI DSS scope?
It can change which systems handle account data, but the result depends on the checkout and token architecture. Outsourcing does not remove the merchant's duty to manage the provider and validate the applicable PCI DSS scope.
What is the most important migration question?
Ask whether payment credentials and route configuration can be exported in a usable form, under what conditions, and whether connected processors will accept the transferred tokens. A generic data-export promise is not enough.