> ## Documentation Index
> Fetch the complete documentation index at: https://nextgen-docs.enfuce.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cardholder Authentication

Before a token can be activated, the cardholder may need to verify their identity.

Authentication requirements depend on the requirements defined by the card Scheme and wallet provider, as well as your implementation of the authentication experience. Authentication confirms whether the person provisioning the card is the legitimate cardholder.

The token is activated and can be used for payments, if the cardholder is successfully authenticated.

## Authentication Methods

<Info>You do not need to support all authentication methods — the authentication methods that you must support depend on the wallet provider's requirements and your implementation approach.</Info>

Enfuce currently supports the following authentication methods for wallet provisioning:

<AccordionGroup>
  <Accordion title="In-app Authentication">
    <div style={{marginLeft:'20px'}}>
      The cardholder is authenticated through the customer’s application.

      Depending on the Scheme requirements and wallet provider requirements, additional verification may be required even if the cardholder is already logged in.
    </div>
  </Accordion>

  <Accordion title="SMS One-Time Password">
    <div style={{marginLeft:'20px'}}>
      A one-time password is sent to the cardholder’s registered mobile number. The cardholder enters the one-time password in the digital wallet application to complete verification and activate the token.
    </div>
  </Accordion>

  <Accordion title="Call Centre Verification">
    <div style={{marginLeft:'20px'}}>
      The cardholder contacts the customer’s customer support team to verify their identity.

      <Note>Enfuce does not provide call centre services. You are responsible for operating the customer support function and performing the cardholder verification process.</Note>

      Following successful verification, the token can be activated manually through the Scheme portal or through token management APIs.
    </div>
  </Accordion>
</AccordionGroup>

<Note>Although you do not need to support all authentication methods, implementing the in-app authentication provides a strong cardholder verification experience and reduces the number of provisioning journeys requiring additional checking through other authentication methods.<br /> Many customers of Enfuce implement in-app authentication, as it enables cardholders to be verified within an already authenticated application, rather than relying solely on SMS OTP. For example, Apple Pay requires customers to support SMS OTP and call centre verification. Additional authentication methods, such as in-app authentication, can be implemented to provide a more secure and streamlined cardholder verification experience.</Note>