Multiple payment gateways
Connect and manage multiple payment gateways through Bonza Payments while keeping customer payment activity connected to Salesforce and your wider payment lifecycle.
Part of the Salesforce-native Bonza Payments suiteThe payment starts in Bonza. Stripe — the configured default — will handle the underlying payment processing for this payment. Selection is made here; Bonza does not route payments between gateways on its own.
Plain definition
Multi-gateway payment management allows a business to work with more than one payment gateway within the same payment operation.
Bonza Payments provides a Salesforce-native payment-management layer where businesses can configure supported payment gateways, establish a default gateway and use another configured gateway when appropriate — while keeping payment activity connected to Salesforce.
A payment gateway handles the relevant payment-processing functions. Bonza Payments sits above the gateway layer to manage the wider Salesforce payment experience, customer context and payment lifecycle.
The real problem
A business may begin with one gateway. Over time, payment requirements become more varied — and each new provider risks becoming another disconnected payment process.
VARIATION CAN COME FROM
AND THEN TEAMS ARE LOOKING AT
How many payment systems does our team need to understand just to manage one customer relationship?
Two models
Each one brings a different operational path, a different payment context, a different portal and separate visibility.
A multi-gateway strategy works best when gateway choice is separated from the broader payment-management experience.
The architectural idea
Salesforce provides the business and customer environment in which the wider payment relationship is managed.
Bonza provides the Salesforce-native payment-management layer, connecting the payment journey with customer and operational context.
Gateways handle the relevant underlying payment-processing functions according to their own capabilities and configuration.
Gateway names are examples of configured providers, not partnerships, certifications or endorsements. [Confirm the supported gateway list before launch.]
Core capability
Configure multiple supported payment providers within the Bonza payment environment rather than wiring each one into its own process.
Establish the gateway that appears as the default payment option in the supported Bonza workflow, so the common case needs no decision.
Where appropriate, a user can select another configured gateway for the relevant payment.
Where configured and supported, relevant Bonza customer-facing payment experiences can present available payment options.
Whichever configured gateway is used, the payment stays connected with the broader Salesforce payment context.
Default behaviour
This payment will be processed through Stripe, the configured default.
A configured starting selection. It appears first in the supported workflow, and a user can choose another configured gateway when the situation calls for it.
Bonza does not route payments between gateways on its own — no least-cost, dynamic, geographic or success-rate routing, no cascading, failover, load balancing or automatic retry through another gateway. Gateway choice is a human decision in the supported workflow.
How it works
Internal payment experience
The point isn't the dropdown. It's that the team stays inside the Bonza payment experience while selecting from configured payment options — no second portal, no lost customer context.
Try it: change the gateway and the payment stays exactly where it is.
Customer payment experience
Bonza supports customer-facing payment experiences, including Salesforce Experience Cloud scenarios. Where multiple options are configured for the relevant experience, the customer chooses before paying.
THE CUSTOMER JOURNEY
What the customer actually sees — gateway names or more general payment options — depends on how the experience is configured. The labels above are deliberately neutral rather than an invented checkout. [Confirm the customer-facing option labels before launch.]
IN SALESFORCE EXPERIENCE CLOUD
Across the lifecycle
Available payment methods and capabilities can vary by gateway and configuration. Recurring collection and refund behaviour in particular are not identical across providers — what a given gateway supports depends on that gateway and your implementation.
Choose the appropriate configured gateway for an individual payment.
Recurring capabilities depend on the relevant configured gateway and implementation. An arrangement does not freely switch gateways mid-cycle, stored payment methods and tokens do not move between gateways, and Bonza does not retry through another gateway.
Post-payment activity stays connected to the gateway behind the original payment. Refund capabilities and processing behaviour can vary by gateway.
An honest caveat
Using multiple payment gateways does not mean every gateway has identical capabilities. A multi-gateway strategy isn't about pretending providers are interchangeable — it's about a payment architecture that can work with different configured providers while respecting what each one actually does.
Different capability sets. One payment operation.
We don't publish gateway-specific feature claims here. What a given provider supports for your implementation is worth confirming directly. [Confirm per-gateway capabilities before launch.]
Buyer education
A business may work with different payment providers across its operations.
Different providers may support different payment methods depending on configuration and market.
Provider requirements can change as the business enters new markets or adds new payment scenarios.
Different business units or acquired operations may already work with different gateways.
Different payment scenarios may call for different configured payment options.
Avoid designing the entire payment-management architecture around only one provider.
Businesses evaluate multi-gateway strategies for other reasons too — fees, success rates, resilience. Those are industry considerations, not Bonza outcomes: we don't promise reduced fees, higher success rates, automatic resilience or better uptime.
Gateway configuration
Connected, configured, default, available — that's what this workspace reports. There are no gateway health scores, uptime readouts, success-rate analytics, fee comparisons, settlement status, routing weights or priority percentages here, because Bonza does not optimise between gateways on your behalf. [Confirm the final field and action set before launch.]
Payment Command Center
Payment operations should be understandable at the Bonza level, not only by opening individual gateway portals. Filter the illustrative activity below by gateway.
| Customer | Amount | Gateway | Status |
|---|---|---|---|
| Acme Customer | $1,200 | Stripe | Paid |
| Northstar Industries | $850 | Razorpay | Paid |
| Global Corp | $2,100 | PayU | Processing |
| Harbor Academy | $3,150 | Stripe | Paid |
| Meridian Clinics | $1,100 | Razorpay | Paid |
No illustrative payments for that gateway.
Payment activity is readable together in Bonza. This is operational visibility — not consolidated settlement or accounting reconciliation across gateways.
Two architectures
The multi-gateway model isn't universally right for every company. A business that only needs one gateway can use a straightforward single-gateway configuration — the value of multi-gateway capability becomes relevant as payment requirements expand.
Positioning
COMPLETE PAYMENT MANAGEMENT LAYER
PAYMENT GATEWAY LAYER
Gateways are one layer of the Bonza platform. They are not the whole product — the payment lifecycle above them is where most of the work happens.
Explore the Bonza Payments Suite →What changes
We don't claim lower transaction costs, higher conversion or authorisation rates, guaranteed availability, reduced payment failures or automatic redundancy — those depend on your providers and your configuration, not on Bonza.
Why Bonza
Payment activity stays connected with Salesforce business and customer context, whichever gateway processed it.
Support more than one payment gateway within the Bonza payment environment.
Set a configured gateway as the normal selection, so the common case stays simple.
Use another configured gateway where the supported workflow requires it.
Extend relevant configured payment options into customer-facing payment journeys where supported.
Keep gateway infrastructure connected with payments, recurring collections, invoices, receivables, refunds, credits and payment intelligence.
FAQ
A payment gateway is the provider that handles the relevant payment-processing functions for a transaction. It sits beneath the payment-management layer: Bonza manages the payment experience, customer context and lifecycle, and the gateway performs the processing according to its own capabilities and configuration.
Multi-gateway payment management allows a business to work with more than one payment gateway within the same payment operation — configuring supported gateways, setting a default, and using another configured gateway where appropriate, without building a separate payment process for each one.
Salesforce itself does not process payments. With a Salesforce-native payment-management layer such as Bonza Payments, a business can configure multiple supported gateways and keep the resulting payment activity connected to Salesforce customer records.
Yes. Multiple supported payment gateways can be configured within the Bonza payment environment, with one set as the default and others available for selection where the supported workflow allows.
Bonza can be configured with supported payment gateways. Examples discussed for the platform include Stripe, Razorpay and PayU. This is not an exhaustive list — available integrations and capabilities depend on the implementation, so confirm the current supported set for your project.
Yes. A configured gateway can be established as the default, so it appears as the normal starting selection in the supported workflow rather than requiring a decision on every payment.
Yes, where appropriate. The default is a starting point rather than a lock — a user can select another configured gateway for the relevant payment within the supported workflow.
Where configured and supported, relevant customer-facing payment experiences can present available payment options. What the customer sees — gateway names or more general payment options — depends on how that experience has been configured.
Bonza supports customer payment experiences including Experience Cloud scenarios, and the relevant configured payment options can be presented there. The selected gateway performs the payment processing; Salesforce itself does not process the payment.
Recurring payment activity runs through the relevant configured gateway, and recurring capabilities depend on that gateway and your implementation. A recurring arrangement does not freely switch gateways mid-cycle, stored payment methods and tokens do not transfer between gateways, and Bonza does not automatically retry a collection through a different gateway.
A refund stays connected to the gateway behind the original payment and is managed through that gateway's relevant refund process, with the activity visible in Bonza payment history. Refund capabilities and processing behaviour can vary by gateway.
No. Bonza does not perform automatic, intelligent, least-cost, dynamic, geographic or success-rate-based routing, and it does not cascade, fail over, load balance or retry through another gateway. A default gateway is configured, and another configured gateway can be selected within the supported workflow — the choice is made by a person, not by the system.
No. Bonza Payments is the Salesforce-native payment-management layer that works with configured payment gateways for the relevant payment-processing functions. It is not a gateway, a payment processor, a merchant acquirer or a bank, and it is not a replacement for the gateway you choose.
No. Supported payment methods, currencies, markets, recurring-payment functionality, refund behaviour, technical requirements, merchant configuration, settlement behaviour and fees can all vary by gateway and configuration. A multi-gateway architecture works with those differences rather than pretending they don't exist.
See how Bonza Payments helps you manage multiple configured payment gateways while keeping customer payment activity connected to Salesforce and your wider payment lifecycle.