Widget Registration Tokens

PIPE Registration Tokens

PIPE allows you to securely collect and store (non-)card data from shoppers for future usage e.g. recurring payments, one-click payments.

To better understand registration tokens in eCommerce, please read Tokenization Guide.
To use network tokens issued by the card networks for your payments, please refer to PIPE Network Tokens.

Use cases

Standalone tokenization

The merchant collects card data from the shopper via the tokenization widget and initiates the registration tokenization. No payment request/flow is involved. A registration token is synchronously provisioned and returned to the merchant so it can be stored. The registration token can then be used in subsequent payments.


How it works

Prepare the checkout

Send the request parameters server-to-server to prepare the registration form.

Create the registration form

Display the registration form on your checkout page. Shopper submits the card information to create registration token.

Get the registration status

Find out if the registration token was successful.

OPTIONAL

Send payment using the token

Send payment using the stored registration token.

Transactions:
RG
RG
DB
DB

1. Prepare the checkout

Perform a server-to-server POST request to prepare the checkout with the required customer data, including createRegistration=true but excluding paymentType. The response to a successful request is an id required in the second step to create the registration form.

Sample request:

2. Create the registration form

Create the registration form by adding the following lines of HTML/JavaScript to your page:

  • With the checkoutId received from first step
    <script src="https://eu-test.oppwa.com/v1/paymentWidgets.js?checkoutId={checkoutId}/registration"></script>
  • With the shopperResultUrl as the page on your site where the end consumer should be redirected after the tokenization is complete
    <form action="{shopperResultUrl}" class="paymentWidgets" data-brands="VISA MASTER AMEX"></form>

Sample form:

3. Get the registration status

Once the tokenization request is processed, the customer is redirected to your shopperResultUrl along with a GET parameter resourcePath.

resourcePath=/v1/checkouts/{checkoutId}/registration

Sample request:

4. Send payment using the token

Perform a server-to-server POST request over the registration token retrieved in the previous step. Alternatively, use one-click checkout to authorize the payment with a selected stored registration token.

Sample request:


See also