FILTER BY TAG
pilot

Step-up Authentication for Registration

When you request authentication options for a tokenized card, the response indicates which
Payment Passkey
sequence to take for the current device and token combination:
  • AUTHENTICATE
  • AUTHENTICATION_REGISTRATION
  • STEP_UP_AUTHENTICATION
This section describes what to do when the
action
field in your request to the
/tms/v2/tokenized-cards/
{tokenId}
/authentication-options
endpoint returns a value of
STEP_UP_AUTHENTICATION
. When the response returns
STEP_UP_AUTHENTICATION
, the issuer requires additional verification before the device can be approved and passkey registration can proceed. Example verification includes one-time password (OTP), issuer application approval, or phone verification. For information about the
Payment Passkey
flow, see Payment Passkey.
These step-up options are available:
One-time password (OTP)
You can get a one-time password using these methods:
  • Email OTP
    :
    stepUpOptions.method
    is set to
    OTP_EMAIL
    .
  • Issuer account OTP
    :
    stepUpOptions.method
    is set to
    OTP_ONLINE_BANKING
    .
  • SMS OTP
    :
    stepUpOptions.method
    is set to
    OTP_SMS
    .
Issuer Application
You can authenticate in an issuer application using these methods:
  • Issuer application with backend Visa integration
    :
    stepUpOptions.method
    is set to
    APP_TO_APP
    .
  • Issuer application returns issuer authentication code
    :
    stepUpOptions.method
    is set to
    APP_TO_APP
    .
  • Issuer
    3-D Secure
    :
    stepUpOptions.method
    is set to
    APP_TO_APP
    and
    deviceInformation.platformType
    is set to
    WEB
    .
Phone Issuer
You can authenticate over the phone using these methods:
  • Cardholder calls issuer call center
    :
    stepUpOptions.method
    is set to
    CUSTOMERSERVICE
    .
  • Issuer calls cardholder
    :
    stepUpOptions.method
    is set to
    OUTBOUNDCALL
    .