PG Agnostic Native OTP
End-to-end card payments, all within your app!
Card transaction flow
When a card transaction is initiated, customers are redirected to the respective Bank's OTP page (called ACS page) to enter the OTP and complete the transaction. This redirection is necessary for OTP generation and verification, but the UX / UI varies between banks and may not often be optimised for mobile screens. Multiple browser redirects may be required, leading to a less-than-optimal user experience.
Juspay Native OTP card transaction flow
As a solution, Juspay has introduced a seamless OTP page that will be native to your app or website. This means your customers can enter their OTPs comfortably within your app or website, without any re-directions to different Bank pages. Juspay native OTP screens are configurable to easily blend with your checkout page.
Your customers will still have access to familiar options such as Resend OTP and the ability to redirect to the bank page from this native OTP screen.
Feature Details
Payment Methods supported: Debit Card & Credit Card
Platforms Supported: Android, iOS, Web
Supported Juspay Integrations :
Juspay HyperCheckout (Payment Page)
Juspay Express Checkout SDK (EC Headless SDK)
UX Configurable: Yes
Merchants live with native OTP flow: Bigbasket, Junglee Games, physics etc
Feature Benefits
Customer Journey
For PG-dependent Native OTP flow, please refer to the documentation below.
Frequently Asked Questions
Will this feature work for all card brands?
When does the customer see the native OTP page during a transaction?
- Have questions?
- Need help? Contact support
- LLM? Read llms.txt

