---
page_source: https://docs.juspay.io/dotp-v2/docs/native-otp/overview
page_title: Overview
---


# 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

[Video](https://youtu.be/vyIg5YoLPLA)




### **Feature Benefits** 



![Image](https://dth95m2xtyv8v.cloudfront.net/tesseract/assets/dotp/Screenshot%202023-12-29%20at%209.27.37%20AM.png)




### **Customer Journey** 



![Image](https://dth95m2xtyv8v.cloudfront.net/tesseract/assets/dotp/DOTP%20User%20Journey.png)




#### For PG-dependent Native OTP flow, please refer to the documentation below.



👉 [DOTP – Native OTP Overview](https://juspay.io/in/docs/dotp/docs/native-otp/overview)

**Frequently Asked Questions** 

## FAQs:

### Will this feature work for all card brands?

Native OTP page is a **Card BIN based feature** . A card bank identification number (BIN) represents the first six to nine digits on a credit card. This card BIN identifies the financial institution that issued the card and is a security measure to protect both consumers and merchants engaging in online transactions.

### When does the customer see the native OTP page during a transaction?

The native OTP page is displayed to the customer when the card bin eligibility check confirms it is supported. This occurs after the customer has entered their card details.

If the card bin does not support native OTP, customers will see the Bank OTP page (ACS page) instead.

The card bin eligibility step is handled by Juspay for Hypercheckout integration (Payment Page) and Express Checkout SDK integration .