# Tokenization

Tokenization allows you to store payment data for later use. This can be useful for recurring and/or one-click payment scenarios.

This guide will describe how you can store account details using Primeiro Pay and how you can subsequently use the stored account details.

### Storing the payment data

PrimeiroPay provides two options for storing the payment data:

* [Store the data during a payment](https://developers.primeiropay.com/tokenization#store-the-data-during-a-payment): When a shopper is checking out for the first time, he has to fill in his complete payment- and address data. Use this option to automatically store his data during the payment for reuse in later transactions.
* [Store the data as stand-alone](https://developers.primeiropay.com/tokenization#store-the-data-as-stand-alone): If your site provides shoppers with an administrative area where they can register their payment details independent of a checkout-process, this option is for you.

#### Store the data during a payment

You have two options for achieving this:

* [Merchant-determined](https://developers.primeiropay.com/tokenization#merchant-determined-tokenization) tokenization
* [Shopper-determined](https://developers.primeiropay.com/tokenization#shopper-determined-tokenization) tokenization.

#### **Merchant-determined tokenization**

During the checkout process you can store the data by adding an additional parameter to the normal prepare checkout request as described in [step 1 of the Primeiro Pay checkout](https://primeiropay.docs.oppwa.com/integration-guide#CNPStep1):

```
createRegistration=true
```

After the account holder has filled in their account information and are redirected back to your `shopperResultUrl`, you can retrieve the response information as usual ([step 3](https://primeiropay.docs.oppwa.com/integration-guide#CNPStep3)). This time, however, the response will include a `registrationId` (token) and useful card information that you can store for future 'one-click payment' requests.

#### **Shopper-determined tokenization**

When the payment form is displayed as described in [step 2 of the Primeiro Pay checkout](https://primeiropay.docs.oppwa.com/integration-guide#CNPStep2), you can extend the form to display an option to your customer that allows him store his account data.

This can be achieved very easily by using the [Primeiro Pay API](https://primeiropay.docs.oppwa.com/widget-api). You can see an example implementation of this in the "store payment details" use case that is part of the[ Advanced Options](https://developers.primeiropay.com/getting-started/hosted-checkout/copy-and-pay-1/advanced-options) tutorial.

[![](https://primeiropay.docs.oppwa.com/sites/default/files/tokenizationCNPForm.png)](https://primeiropay.docs.oppwa.com/advanced-options)

After the account holder has filled in his account information and was redirected to the  `shopperResultUrl`, you can retrieve the response information as usual ([step 3](https://primeiropay.docs.oppwa.com/integration-guide#CNPStep3)). This time, however, the response will include a `registrationId` (token) and useful card information that you can store for future 'one-click payment' requests.

#### Store the data as stand-alone

With Primeiro Pay it is also possible to create a just registration separate from any later payment.

A registration-only transaction with Primeiro Pay is basically using the same workflow and parameters as a payment.

You only have to change two parameters in [**step1**](https://primeiropay.docs.oppwa.com/integration-guide#CNPStep1):

* `createRegistration=true` has to be sent.
* `paymentType` should not be sent.

Now Primeiro Pay **automatically adapts the workflow** for handling a registration:

* In [step2](https://primeiropay.docs.oppwa.com/integration-guide#CNPStep2) Primeiro Pay will render the payment form as usual, but send the form to `https://{test.}oppwa.com/v1/checkouts/{checkoutId}/`**`registration`**
* In [step3](https://primeiropay.docs.oppwa.com/integration-guide#CNPStep3) you'll get back a resourcePath pointing to you to query for a registration's result: `resourcePath=/v1/checkouts/{checkoutId}/`**`registration`**

IMPORTANT: The baseUrl (that is prepended to the resourcePath) must end in a "/", e.g. "<https://test.oppwa.com/>".

### Using the payment data

#### Use Case 1: Recurring Payment

Based on the stored account details, recurring payments become very simple to achieve.

All you need to do is to add the parameter `recurringType` to your request to the /checkouts endpoint (see [step1](https://primeiropay.docs.oppwa.com/integration-guide#CNPStep1)):

* For the initial payment request you should send the `recurringType` with value `INITIAL`.
* For any subsequent payment you should send the `recurringType` with value `REPEATED`.

The [Recurring Payment tutorial](https://developers.primeiropay.com/getting-started/server-to-server-api/recurring-1) explains this scenario in more detail.

#### Use Case 2: One-Click Payment

After storing a customer's account details, it is possible to offer a 'one-click payment' checkout, to simplify subsequent purchases.

Basically you're using the token you've received in the original payment's response in the field `registrationId` to reference and even prefill a customer's payment form.

![one-click checkout ](https://primeiropay.docs.oppwa.com/sites/default/files/one-click-checkout-mini.png)

The Server-to-Server [One-click Payment tutorial](https://primeiropay.docs.oppwa.com/tutorials/integration-guide/one-click)

Or

Primeiro Pay [One-click Checkout tutorial](https://primeiropay.docs.oppwa.com/tutorials/integration-guide/one-click) explains this scenario in more detail.