Payment Modes
Orbit processes payments across every major payment mode used in India. Whether your customers prefer UPI, cards, Netbanking, wallets, EMI, or Pay Later, Orbit handles the processing through a single integration while routing each transaction to the appropriate payment partner.
This page covers what each payment mode supports at a product level. For partner-specific coverage, see Payment Partners.
What Orbit Supports
Orbit supports seven core payment mode categories, each backed by multiple payment partner integrations for reliability and coverage.
| Payment Mode | Partner Count | Key Highlights |
|---|---|---|
| Cards | 21 | Credit, debit, prepaid; 3DS; international cards |
| UPI | 18 | Intent, QR, and Collect flows |
| Netbanking | 18 | 70+ banks, retail and corporate |
| Wallets | 13 | 10+ wallet providers |
| EMI | 6 | Card EMI and cardless EMI |
| Pay Later | 4 | Simpl, LazyPay, Mobikwik Zip, Ola Postpaid |
| Cash on Delivery | — | Order-level COD support |
Partner coverage can vary by merchant configuration and routing rules. The counts above reflect product-level support; your available options may differ.
Card Processing
Orbit supports card payments across credit, debit, and prepaid cards through 21 payment partners. Card processing in Orbit includes detection and validation (identifying the card network, issuer bank, and card type), 3D Secure authentication where required, and support for multiple input formats including raw PAN, encrypted payloads, and token-based flows.
International card processing is supported for scenarios where the card country or currency differs from the order currency. When currency conversion is involved, Orbit applies automatic or dynamic currency conversion as configured. For details on currency handling, see Multi-Currency.
Cards also support third-party verification (TPV) for beneficiary account validation where required.
Card Types and Networks
Orbit processes cards across all major networks used in India and internationally: Visa, Mastercard, RuPay, American Express, and Diners Club. Both credit and debit cards are supported on each network, subject to partner availability.
Network detection happens automatically through BIN (Bank Identification Number) lookup. When a customer enters their card number, Orbit identifies the network, issuer bank, and card category (credit, debit, or prepaid) to determine processing rules and partner routing.
Multi-Format Processing
Orbit accepts card input in multiple formats to support different integration patterns and security requirements:
- Raw PAN -- the full card number submitted directly, typically from a merchant's own checkout form.
- Encrypted payloads -- card data encrypted at the client before transmission, reducing PCI scope for the merchant.
- Network tokens -- tokenized card credentials issued by card networks (Visa, Mastercard, RuPay) that replace the actual PAN for recurring or stored-card flows.
This flexibility allows merchants to choose the input format that matches their security posture and integration architecture. Domestic, international, and prepaid cards are all supported across these formats.
Security and Validation
Orbit applies multiple security layers during card processing. 3D Secure (3DS) authentication is handled where required by the card network or issuer, with Orbit managing the redirect and verification flow transparently.
BIN detection identifies the card's network, issuer, and type at entry time, enabling Orbit to apply the correct processing rules before the transaction reaches a payment partner. Card validation checks format, length, and Luhn correctness to reject invalid cards early.
For stored-card scenarios, tokenization through card network token frameworks allows merchants to process repeat payments without storing raw card data.
International Cards
Orbit supports cross-border card processing for transactions where the card-issuing country or currency differs from the merchant's order currency. Partners such as Checkout.com, HDFC MPGS, PayGlocal, and Unlimit provide international card acceptance.
When currency conversion is needed, Orbit applies automatic currency conversion (ACC) or dynamic currency conversion (DCC) based on merchant configuration. International card transactions follow the same processing pipeline as domestic cards, with additional currency and country checks applied during routing. For full details on currency handling, see Multi-Currency.
UPI Processing
Orbit supports three UPI flows, each suited to different customer contexts:
- Intent -- a customer-initiated flow that launches a UPI app directly. This is the most common flow on mobile devices.
- QR -- a customer-initiated flow that generates a scannable QR code. This is common on desktop and web experiences.
- Collect -- a merchant-initiated flow that sends a payment request to a customer's UPI ID (VPA).
UPI processing in Orbit includes VPA validation (format and provider-assisted checks), QR code generation for scan-and-pay flows, cross-platform intent intelligence with app detection and deep linking, and post-transaction intelligence that extracts instrument and app information from partner responses.
Orbit processes UPI payments through 18 payment partners. UPI also supports TPV for beneficiary account verification on supported flows.
UPI Flows
The Collect flow sends a payment request to a customer's VPA (Virtual Payment Address). The customer receives the request in their UPI app, reviews the amount and merchant details, and approves the payment. This flow is suited to scenarios where the customer provides their UPI ID upfront and the merchant initiates the transaction.
The Intent flow redirects the customer to a UPI app installed on their device. Orbit detects available UPI apps on the customer's device, generates deep links for each app, and launches the selected app directly. This is the fastest flow on mobile devices since the customer approves payment within their UPI app without manual entry.
The QR flow generates a scannable QR code that the customer scans with any UPI app. This is the standard approach for desktop and web checkout where a direct app redirect is not possible.
UPI Intelligence
Orbit applies multiple layers of intelligence to improve UPI payment success. VPA validation checks the handle format and verifies VPA existence through provider-assisted lookups before initiating a transaction, reducing failures from invalid addresses.
For Intent flows, Orbit performs cross-platform app detection to identify which UPI apps are available on the customer's device. This allows the checkout experience to present only apps that the customer actually has installed, with correct deep links for each platform (Android and iOS).
After a UPI transaction completes, Orbit extracts instrument and app information from the payment partner's response. This post-transaction intelligence feeds into analytics and helps improve routing decisions for future transactions.
Netbanking
Orbit routes Netbanking payments through 18 payment partners and supports 70+ banks, including all major public and private sector banks such as SBI, HDFC, ICICI, Axis, Kotak, PNB, Canara Bank, and Bank of Baroda. Both retail and corporate Netbanking are supported where the payment partner allows.
Netbanking supports TPV for beneficiary account verification on supported payment partners.
Wallets
Orbit processes wallet payments through 13 payment partners across 10+ wallet providers including Paytm, PhonePe, Freecharge, Mobikwik, and Amazon Pay. Wallet transactions are routed through the configured payment partner based on wallet provider availability and routing rules.
EMI Processing
Orbit supports two types of EMI processing:
- Card EMI -- EMI executed on a credit or debit card, where the issuer bank determines eligible tenure options and schemes. Card EMI is processed through payment partners such as PayU, Razorpay, Easebuzz, Pinelabs, and Razorpay CC.
- Cardless EMI -- EMI executed without a physical card, through a cardless EMI provider. Cardless EMI is processed through PayU, Razorpay, and Cashfree. Issuer and provider availability varies by merchant configuration.
For the customer-facing affordability experience (showing EMI options during checkout), see Boostr.
Card EMI
Card EMI converts a card transaction into monthly installments at checkout. The issuer bank (such as HDFC, ICICI, Axis, Kotak, or SBI) determines which tenure options and interest schemes are available for a given card. Orbit retrieves eligible EMI plans from the payment partner and presents them during checkout.
Both credit and debit card EMI are supported, though debit card EMI availability depends on the issuer bank and payment partner. Card EMI is processed through PayU, Razorpay, Easebuzz, Pine Labs / Plural, and Razorpay CC.
Cardless EMI
Cardless EMI allows customers to pay in installments without using a physical card. Instead, the customer authenticates with a cardless EMI provider (such as ZestMoney, FlexiPay, or other provider entities) through OTP verification and eligibility checks managed by the provider.
Orbit processes cardless EMI through PayU, Razorpay, and Cashfree. The available cardless EMI providers and their eligibility criteria are data-driven and vary by merchant configuration. Unlike card EMI, the issuer or provider entities in cardless EMI are distinct from payment partners.
Pay Later
Orbit supports Pay Later processing through four providers: Simpl, LazyPay, Mobikwik Zip, and Ola Postpaid. Each provider has its own authentication and eligibility flows, including OTP verification and account discovery. Orbit handles provider-specific execution while keeping the integration surface consistent for merchants.
Loyalty Points
Orbit supports loyalty and reward points as a payment mode, allowing customers to redeem accumulated points (such as NeuCoins) during checkout. Loyalty point redemption is processed through the associated payment partner, with Orbit handling point balance inquiry, partial or full redemption, and settlement reconciliation.
When a customer opts to pay with loyalty points, Orbit verifies the available balance and applies the redemption against the order total. If the points balance does not cover the full amount, the remaining balance can be paid through another payment mode in a split-payment flow.
Cash on Delivery
Orbit supports Cash on Delivery (COD) as an order-level payment mode. COD orders are tracked through the standard order lifecycle but do not involve online payment processing at checkout time.
Payment Partner Coverage
For the full matrix of which payment partners support each payment mode, see the Payment Partners page. Partner coverage can vary by merchant configuration and routing rules.