> ## 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.

# Wallet Provisioning

Provisioning is the process of creating a payment token and securely linking it to a card. Once provisioning is complete, the token can be used for payments through the digital wallet.

Provisioning can be initiated in two main ways:

* Push provisioning starts from the customer's application or digital channel.
* Manual provisioning starts from the wallet application.

<AccordionGroup>
  <Accordion title="Push Provisioning">
    <div style={{marginLeft: '20px'}}>
      Push provisioning, also known as in-app provisioning, is initiated from your application. In this flow, a cardholder selects a card in the customer’s application and chooses to add it to a digital wallet.

      <Steps>
        <Step title="First Step">
          The cardholder opens your application and selects the card they want to add to a digital wallet.
        </Step>

        <Step title="Second Step">
          Your system sends a request to the Enfuce Wallet API to retrieve wallet provisioning data.
        </Step>

        <Step title="Third Step">
          Enfuce generates and returns the provisioning data that the wallet provider requires.
        </Step>

        <Step title="Fourth Step">
          You transmit the provisioning data to the wallet provider using the wallet provider’s Software Development Kit (SDK).
        </Step>

        <Step title="Fifth Step">
          The wallet provider forwards the request to the Scheme’s tokenisation service, such as Mastercard Digital Enablement Service (MDES) or Visa Token Service (VTS).
        </Step>

        <Step title="Sixth Step">
          Depending on Scheme requirements, the wallet provider requirements, and your authentication implementation, the cardholder may need to complete additional authentication before the token is activated.
        </Step>

        <Step title="Seventh Step">
          The Scheme creates a payment token and links it to the underlying card.
        </Step>

        <Step title="Eighth Step">
          The wallet provider provisions the token to the device, allowing the cardholder to make payments using the digital wallet.
        </Step>
      </Steps>
    </div>
  </Accordion>

  <Accordion title="Manual Provisioning">
    <div style={{marginLeft: '20px'}}>
      Manual provisioning initiates from a specific wallet application, rather than your application. In this flow, the cardholder adds the card directly in the wallet application — enters the card details manually or scans the physical card.

      <Steps>
        <Step title="First Step">
          The cardholder opens the digital wallet application.
        </Step>

        <Step title="Second Step">
          The cardholder enters the card details manually or scans the physical card.
        </Step>

        <Step title="Third Step">
          The wallet provider sends a provisioning request to the Scheme’s tokenisation service, such as MDES or VTS.
        </Step>

        <Step title="Fourth Step">
          The Scheme exchanges the information required for token provisioning with Enfuce, including card and token-related validation data.
        </Step>

        <Step title="Fifth Step">
          Depending on the Scheme requirements, the wallet provider requirements, and your authentication implementation, the cardholder may need to complete additional authentication before the token is activated.
        </Step>

        <Step title="Sixth Step">
          Once all requirements are met, the Scheme creates a payment token and links it to the underlying card.
        </Step>

        <Step title="Seventh Step">
          The wallet provider provisions the token to the device, allowing the cardholder to make payments using the digital wallet.
        </Step>
      </Steps>
    </div>
  </Accordion>
</AccordionGroup>

## Related APIs

* [Apple Pay Push Provisioning](https://nextgen-docs.enfuce.com/api/wallet/apple-pay)
* [Google Pay Push Provisioning](https://nextgen-docs.enfuce.com/api/wallet/google-pay)
* [Samsung Pay Push Provisioning](https://nextgen-docs.enfuce.com/api/wallet/samsung-pay)
