Platform capability
Multiple payment providers, working as one
Run gateways, aggregators and acquiring banks side by side. Use each one where it performs best, keep a second route for every method, and change the mix without touching your code.
- Different providers for different methods
- A second route for everything that matters
- New providers tested on a small share first
A dashboard list of connected providers A, B and C with the payment methods each supports. Provider D is added and switched on for cards. The card traffic split changes from A 60% and C 40% to A 45%, C 35% and D 20%, with no change to the merchant's integration.
Why more than one
When one provider stops being enough
One provider is the right call when you're starting out. It becomes a constraint as volume grows. Coverage gaps appear (international cards, EMI, a particular wallet), approval rates for some methods lag, and every incident at that provider takes your whole checkout down.
There's a commercial side too. With a single provider you have no leverage on pricing, and your settlements depend entirely on one relationship. That matters when a provider holds funds during a risk review.
Common triggers
- A method or market your provider doesn't support well
- An incident that took payments down for an evening
- Settlements held during a provider's risk review
- A pricing negotiation with no alternative on the table
What you can connect
Provider types that sit behind Peneu
Which specific providers are available for your business is confirmed during onboarding. We only name a provider on this site when there's a live connection with it.
- 01
Payment gateways and aggregators
Broad method coverage (cards, UPI, netbanking, wallets) through one provider relationship.
- 02
Acquiring banks
Direct card and UPI acquiring, often preferred for high-value or high-volume flows.
- 03
Cross-border providers
Acceptance of international cards and currencies, with settlement in India.
- 04
Payout banks
Outbound transfers over IMPS, NEFT, RTGS and UPI, with more than one bank for resilience.
- 05
Verification and mandates
KYC and bank-account checks, eNACH and UPI Autopay, used alongside payments.
- 06
Bill payments
BBPS biller and agent connectivity for businesses that collect or pay bills.
An example
What a provider mix can look like
This is an example, not a recommendation. The right mix depends on your methods, ticket sizes and markets.
| Method | Primary | Second route | Why |
|---|---|---|---|
| UPI | Provider A | Provider B | Two PSPs, so one incident doesn't stop UPI |
| Domestic cards | Acquiring bank | Provider A | Direct acquiring for volume, with an aggregator as backup |
| Netbanking | Provider A | Provider C | Bank coverage differs between providers |
| International cards | Provider C | — | Needs a cross-border-capable provider |
| Card EMI | Provider D | — | Issuer EMI coverage |
How it works
Adding a provider
- 01
Provider onboarding
The provider runs its merchant checks and you agree terms with it. We'll tell you what that provider asks for, so there are no surprises.
- 02
Connect it to Peneu
Its credentials are stored encrypted, separately for sandbox and production. They're never exposed to your frontend or to other merchants.
- 03
Start small
Give it a small share of one method, say 5–10% of UPI, and compare its success rate and response time with your current provider on the same traffic.
- 04
Scale on evidence
Increase its share, or make it the primary for a method, once the numbers support it. Your integration never changes.
Worth knowing
Tokens and mandates belong to a provider
Saved cards, tokenised under RBI's card-on-file rules, and recurring mandates (eNACH or UPI Autopay) are created with a specific provider and stay with it. Routing respects that: a recurring charge goes to the provider that holds its mandate.
Moving existing tokens or mandates from one provider to another is a separate, provider-dependent process. It isn't a routing change.
Evaluating it
Questions to ask about this, of any provider
Use these with any platform, including Peneu. For Peneu, what's available for your business is confirmed during onboarding.
- Who contracts with each provider?
- It decides who you call about settlements and disputes, and where your money sits. Get it in writing.
- How are settlements from different providers reported?
- Several settlement calendars and formats are the main cost of running more than one provider.
- Can a provider be added or removed without code changes?
- The point of several providers is flexibility; check how much it really takes.
- How are refunds handled for payments made through a provider you've stopped using?
- Old payments still need refunds and dispute responses for months.
FAQ
Questions about multiple payment providers
Do I sign up with each provider separately?
Each provider onboards your business under its own checks and agreement. Peneu handles the technical connection and helps you through what each provider needs.
How many providers should I use?
For most businesses, two per important method is the practical sweet spot. A third adds resilience or coverage in specific cases, but each provider also adds reconciliation and relationship work.
Who settles the money?
Each provider settles to your bank account on its own cycle. Peneu reconciles payments against every provider's settlements in one place.
Can I stop using a provider later?
Yes. Disable it and new payments route elsewhere. Refunds for payments it processed still go back through it, which is how refunds work across the industry.
Works together with
Work out your second provider
Tell us your methods, volumes and current provider. We'll suggest where a second route is worth it and what to test first.
Last reviewed . Samples on this page are illustrative.