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

# Wallet operations

> Wallet API enables getting needed data for tokenization and enablement in programs like Apple Pay and Google Pay.

#### Terms used

| Term                | Definition                                                                                                   |
| :------------------ | :----------------------------------------------------------------------------------------------------------- |
| Customer            | End customer using financial institution's mobile application                                                |
| In-app activation   | Wallet provisioning using financial institution app as authentication method                                 |
| In-app provisioning | Mastercard's term for push provisioning                                                                      |
| Push provisioning   | VISA's term for pushing card details from within mobile application. This term will be used in this document |
| Wallet provider     | Such as Apple Pay, Google Pay or Samsung Pay                                                                 |

It's called in two cases:

* *Push provisioning* - this is usually done within issuers own application and card holder does not need to enter any information. Then the different endpoints for push provisioning must be used.
* *In-app activation* - activating a card by manually adding information, then endpoint for generate activation data must be used after authentication of end customer is completed.

<Frame>
  <img src="https://mintcdn.com/enfucefinancialservicesltd-mtje7p526we/qJ7fiLUEp9h1xykh/images/wallet_push_prov.svg?fit=max&auto=format&n=qJ7fiLUEp9h1xykh&q=85&s=68ee226fee6c624cde2599482ec10062" width="1225" height="603" data-path="images/wallet_push_prov.svg" />
</Frame>

In above case the difference between push provisioning and in-app activation is which endpoint that is called in step 3. Note that diagram above is a simplification of full flow in order to explain it from a developer point of view.

<CardGroup cols={2}>
  <Card title="Download OpenAPI specification" href="https://enfuce-public-resources.s3.eu-central-1.amazonaws.com/public/api/cia/external/wallet/wallet.json" />
</CardGroup>

For any questions, contact us:

* [Enfuce Support Portal](https://enfuce.atlassian.net/servicedesk/customer/portal/6)
* [Enfuce website](https://enfuce.com)

<CardGroup cols={2}>
  <Card title="Push Provision" icon="arrow-right" href="/payment/api/push-provision" horizontal />

  <Card title="Activation data" icon="arrow-right" href="/payment/api/activation-data" horizontal />

  <Card title="Get tokens" icon="arrow-right" href="/payment/api/get-tokens" horizontal />

  <Card title="Visa Click2Pay Enroll and manage" icon="arrow-right" href="/payment/api/visa-click2pay-enroll-and-manage/visa-click-to-pay-overview" horizontal />
</CardGroup>