Payment partners are the payment service providers that process the actual fund movement when a customer makes a payment. Nimbbl integrates with multiple payment partners and routes each transaction to the most appropriate one based on Pulse routing rules.
What Are Payment Partners?
Payment Partner Definition
A payment partner (also known as a PSP — payment service provider) is a service that connects merchants to banking and payment networks. When a customer pays through Nimbbl, the payment is routed to one of your configured payment partners, which handles the communication with the customer's bank, UPI app, or wallet provider.
Nimbbl's multi-partner architecture means you are not locked into a single provider. You can configure multiple payment partners and let Pulse route transactions intelligently based on success rates, cost, and business rules.
Available Payment Partners
Nimbbl integrates with 20+ payment partners. The table below lists all active partners with their payment mode support:
| Partner | UPI | Cards | EMI | Netbanking | Wallets | Pay Later | International |
|---|---|---|---|---|---|---|---|
| Bajaj Pay PG | Yes | Yes | -- | Yes | -- | -- | -- |
| BillDesk | Yes | Yes | -- | Yes | Yes | -- | Yes |
| Cashfree | Yes | Yes | -- | Yes | Yes | -- | Yes |
| CCAvenue | Yes | Yes | -- | Yes | Yes | -- | Yes |
| Checkout.com | -- | Yes | -- | -- | -- | -- | Yes |
| Easebuzz | Yes | Yes | Card | Yes | Yes | -- | Yes |
| Freecharge | -- | Yes | -- | Yes | -- | -- | Yes |
| HDFC MPGS | -- | Yes | -- | -- | -- | -- | Yes |
| Ingenico | Yes | Yes | -- | Yes | Yes | -- | Yes |
| LazyPay | -- | -- | -- | -- | -- | Yes | -- |
| Mobikwik Zaakpay | Yes | Yes | -- | Yes | Yes | -- | Yes |
| Mobikwik Zip | -- | -- | -- | -- | -- | Yes | -- |
| Ola Postpaid | -- | -- | -- | -- | -- | Yes | -- |
| Pay10 | Yes | Yes | -- | Yes | Yes | -- | Yes |
| PayGlocal | -- | Yes | -- | Yes | -- | -- | Yes |
| Paytm PG | Yes | Yes | -- | Yes | Yes | -- | Yes |
| PayU | Yes | Yes | Card, Cardless | Yes | Yes | -- | Yes |
| PhonePe PG | Yes | Yes | -- | Yes | -- | -- | Yes |
| Pine Labs / Plural | Yes | Yes | Card | Yes | Yes | -- | Yes |
| Razorpay | Yes | Yes | Card, Cardless | Yes | Yes | -- | Yes |
| Simpl | -- | -- | -- | -- | -- | Yes | -- |
| Unlimit | Yes | Yes | -- | Yes | -- | -- | Yes |
Partner coverage can vary by merchant configuration and routing rules. Contact your Nimbbl account manager for the most current partner availability and onboarding requirements. For detailed EMI issuer availability, see Orbit: Payment Modes.
How Routing Works
When a payment is initiated, Nimbbl determines which payment partner should process it. The routing decision is made by Pulse based on:
- Rule-based routing — deterministic rules you configure (e.g., route all UPI transactions above a certain amount to a specific partner)
- Dynamic routing — AI-driven routing that optimizes for success rates based on real-time performance data
- Fallback and recovery — if the primary partner fails, Pulse can automatically retry with an alternate partner
For details on configuring routing rules, see Pulse Rule-Based Routing and Pulse Dynamic Routing.
Managing Payment Partners
Configuration Overview
Payment partner configuration is managed through the Command Center Developer Settings. Each payment partner requires its own credentials (API keys, secrets) which are configured per environment (test and live).
Key configuration steps:
- Onboard with the payment partner — create a merchant account with the partner and obtain credentials
- Add credentials in Command Center — enter the partner's API keys in Developer Settings
- Configure routing — set up Pulse routing rules to determine when each partner is used
- Test — verify transactions flow correctly in the test environment
Routing Configuration
Routing rules determine which payment partner processes each transaction. You can configure:
- Priority routing — set a primary and fallback partner for each payment mode
- Volume-based routing — distribute transaction volume across partners by percentage
- Conditional routing — route based on transaction attributes (amount, payment mode, card network, etc.)
- Payment partner accounts — when you have multiple credentials (MIDs) for the same partner, route to specific accounts using
cred_label
For complete routing configuration details, see Pulse.