Co-Managed OTP Authentication
In this use case, VCAS will manage the creation and validation of the OTP while leveraging the issuer's existing SMS and/or email aggregator. This is the primary recommended OTP solution for most issuers because it allows VCAS to manage the majority of the authentication experience while leveraging the issuer's current aggregator. This gives the issuer the ability to keep the cardholder OTP experience the same and maintain visibility for cardholder inquiries.
Pros | Cons | RDX Calls |
---|---|---|
VCAS manages OTP creation and validation | An additional API call is required | Stepup |
Issuer uses their own aggregator; providing more confidence in delivery rates, cardholder experience, and access to performance inquiries | Initiate Action |
Co-Managed Flow Diagram
Required RDX Calls:
Updated about 1 year ago