documentation
  • LATAM Payment Methods
  • Integration guide
    • Getting started
      • Payment Methods
      • Payment Types
      • Supported Brands
      • Overview (Authentication and Endpoint)
    • COPYandPAY
      • Customization
      • Advanced Options
      • COPYandPAY API
      • Tokenization
      • Mobile Optimization
    • Server-to-Server
      • Tokenization
  • Manage Payments
    • Backoffice Operations
    • Recurring Payments
    • Installments
    • ZeroAuth
    • Transactions status
  • Instant Payment Notification (IPN) / Webhooks
    • General Information
    • Integration Guide
  • Queries
    • XML Integrator (Queries)
  • Reporting
    • Overview
    • Processed Report
    • Payout Report
    • Report Availability
    • Glossary of Fields
  • Compliance
    • Mandatory parameters by country
    • Test cards by country
    • Customer Identification Number by country (Customer ID)
    • Supported Countries and States
    • Requirements Before Going-Live
  • Reference
    • API Reference
    • Result Codes
  • FAQ
    • COPYandPAY FAQ
    • PCI DSS
    • TLS 1.2
Powered by GitBook
On this page
  • Storing the payment data
  • Store the data during a payment
  • Store the data as stand-alone
  • Using the payment data
  1. Integration guide
  2. COPYandPAY

Tokenization

PreviousCOPYandPAY APINextMobile Optimization

Last updated 6 years ago

Tokenization allows you to store payment data for later use. This can be useful for recurring payment scenarios.

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

  • the payment data

  • the payment data

Storing the payment data

COPYandPAY provides two options for storing the payment data:

  • : 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.

  • : 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 tokenization

During the checkout process you can store the data by adding an additional parameter to the normal prepare checkout request as described in :

createRegistration=true

Shopper-determined tokenization

Store the data as stand-alone

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

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

  • createRegistration=true has to be sent.

  • paymentType should not be sent.

Now COPYandPAY automatically adapts the workflow for handling a registration:

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

Using the payment data

Recurring Payment

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

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

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 (). This time, however, the response will include a registrationId (token) and useful card information that you can store.

When the payment form is displayed as described in , 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 . You can see an example implementation of this in the "store payment details" use case that is part of the tutorial.

After the account holder has filled in his account information and was redirected to the shopperResultUrl, you can retrieve the response information as usual (). This time, however, the response will include a registrationId (token) and useful card information that you can store for future requests.

You only have to change two parameters in :

In COPYandPAY will render the payment form as usual, but send the form to https://{test.}oppwa.com/v1/checkouts/{checkoutId}/registration

In you'll get back a resourcePath pointing to you to query for a registration's result: resourcePath=/v1/checkouts/{checkoutId}/registration

All you need to do is to add the parameter recurringType to your request to the /v1/checkouts endpoint (see ):

COPYandPAY API
Advanced Options
Storing
Using
Store the data during a payment
Store the data as stand-alone
Merchant-determined tokenization
Shopper-determined tokenization
step 1 of the COPYandPAY checkout
step 3
step 2 of the COPYandPAY checkout
step 3
step1
step2
step3
step1
Store payment details