Skip to main content
NetBanking is a bank payment method in India. Customers pay directly from their bank account and confirm each payment in their bank’s internet banking. Payrails processes NetBanking through two payment service providers (PSPs). The flow is the same with each one, but the required request fields differ. Pick a PSP below for its setup steps and request examples.

​
How a NetBanking payment works

NetBanking is a bank redirect payment method:
  1. The customer selects NetBanking at checkout.
  2. Payrails returns a redirect URL from the PSP, and the customer goes to the PSP’s payment page.
  3. The customer chooses their bank, signs in to internet banking, and confirms the payment.
  4. The customer returns to your returnInfo URL.
  5. Payrails receives the final result from the PSP and updates the payment.
Each payment is single-use: the customer confirms every payment on its own. Payrails captures NetBanking payments immediately, so a successful payment is final. To return funds, refund the payment.

​
Supported currencies and countries

NetBanking supports INR (Indian rupee) as its only presentment currency.

​
Integrate NetBanking

Choose the PSP that processes NetBanking for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

dLocal

NetBanking via dLocal

Pine Labs

NetBanking via Pine Labs

​
Compare PSPs

Neither PSP stores a reusable NetBanking token, so Save Instruments and merchant-initiated transactions (MIT) aren’t available for NetBanking.

​
Ways to integrate NetBanking

  • Payrails SDK: the Web SDK shows NetBanking when your workflow returns it as a payment option, and redirects the customer to the PSP. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with netBanking as the paymentMethodCode. Each PSP guide lists the meta fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 2, 2026