Commerce software platforms
Your merchants choose how they get paid. Your platform keeps one API.
Support merchant-owned providers or Orchestra processing where available through one platform integration.
Merchant onboarding decision
Let each merchant choose the payment setup that fits.
Connect a merchant-owned provider account, or offer Orchestra processing where it is available and the merchant is eligible.
Processing availability depends on market, merchant eligibility and configuration.
Two execution routes
One payment request. Two supported merchant paths.
Your platform sends the same payment operation. Merchant configuration determines whether the transaction uses the merchant’s provider account or Orchestra processing where available.
Expand merchant options
Add a payment route. Not another codebase.
Launch another provider or supported processing route while your platform keeps the same request and response contract.
Commerce platform FAQ
Questions you probably have.
Can each merchant use its own provider account?
Yes. Your platform can select the merchant’s configured provider and merchant account for each transaction.
Can merchants keep existing provider relationships?
Yes. Connect the merchant’s own provider account. Your platform keeps the same request and response contract.
When can we offer Orchestra processing?
Where it is available and the merchant is eligible. Availability depends on market, merchant eligibility and configuration.
What if a merchant needs another provider?
Send an integration request. New integrations are added in under two weeks, at no cost, after a feasibility review.
Test the merchant payment flow
Validate both merchant routes before you ship.
Use the sandbox to configure a merchant, send a payment request and inspect the normalized response.
| Route A | Existing provider |
| Route B | Orchestra processing* |
| Response | Normalized |
*Where available.
Free · Up to 100 live requests per month · Unlimited sandbox testing · No credit card required