# Business Overview

Click to Pay is a universal online checkout standard developed jointly by the four major global payment networks — Visa, Mastercard, American Express, and Discover — under the governance of EMVCo. Since it's launch, it has been adopted by thousands of merchants, issuers, and wallet providers worldwide.

At its core, Click to Pay abstracts the consumer's Primary Account Number (PAN) behind a secure network token, enabling merchants to process payments without ever handling raw card data. When a consumer checks out using Click to Pay, their enrolled card credentials are retrieved from the Secure Remote Commerce (SRC) system and delivered to the merchant as a payment token, authorized for that specific transaction. All Click to Pay solutions are indicated by the Click to Pay icon ![](https://www.emvco.com/wp-content/uploads/2022/07/EMV_TECHNOLOGIES_ON-WHITE_emvco-technology-icon_emv-secure-remote-commerce.svg).

### Why Click to Pay Enrollment Matters to Issuers

<span lang="EN-US" style="color: #3d4a5c; mso-ansi-language: EN-US;">For a cardholder to use Click to Pay at checkout, their card must first be enrolled in the relevant SRC System. Without enrollment, the card is invisible to Click to Pay and cannot be presented during checkout — even if the network supports it in principle.</span>

<span lang="EN-US" style="color: #3d4a5c; mso-ansi-language: EN-US;">Issuers drive enrollment. They are the only party that holds the verified cardholder identity, the authoritative card data, and the customer relationship needed to enroll credentials on behalf of or with consent from the cardholder. The Token Management Platform acts as the issuer's API gateway into the Visa SRC and Mastercard MDES systems.</span>

<table border="1" cellpadding="0" cellspacing="0" class="MsoTable15Grid1LightAccent5" id="bkmrk-enrollment-possibili" style="width: 845px; border-collapse: collapse; border: none;" width="595"><tbody><tr style="mso-yfti-irow: -1; mso-yfti-firstrow: yes; mso-yfti-lastfirstrow: yes; height: 31.35pt;"><td style="width: 156.688px; border-width: 1pt 1pt 1.5pt; border-style: solid; border-color: rgb(189, 214, 238) rgb(189, 214, 238) rgb(156, 194, 229); border-image: initial; background: rgb(28, 30, 63); padding: 5.65pt 5.4pt; height: 31.35pt;" width="141">**<span style="font-size: 10.0pt; color: white;">Enrollment possibilities</span>**

</td><td style="width: 230.969px; border-top: 1pt solid rgb(189, 214, 238); border-left: none; border-bottom: 1.5pt solid rgb(156, 194, 229); border-right: 1pt solid rgb(189, 214, 238); background: rgb(28, 30, 63); padding: 5.65pt 5.4pt; height: 31.35pt;" width="95">**<span style="font-size: 10.0pt; color: white;">Description</span>**

</td><td style="width: 289.891px; border-top: 1pt solid rgb(189, 214, 238); border-left: none; border-bottom: 1.5pt solid rgb(156, 194, 229); border-right: 1pt solid rgb(189, 214, 238); background: rgb(28, 30, 63); padding: 5.65pt 5.4pt; height: 31.35pt;" width="161">**<span style="font-size: 10.0pt; color: white;">Business comment</span>**

</td><td style="width: 166.438px; border-top: 1pt solid rgb(189, 214, 238); border-left: none; border-bottom: 1.5pt solid rgb(156, 194, 229); border-right: 1pt solid rgb(189, 214, 238); background: rgb(28, 30, 63); padding: 5.65pt 5.4pt; height: 31.35pt;" width="198">**<span style="font-size: 10.0pt; color: white;">Technical requirements</span>**

</td></tr><tr style="mso-yfti-irow: 0;"><td style="width: 156.688px; border-right: 1pt solid rgb(189, 214, 238); border-bottom: 1pt solid rgb(189, 214, 238); border-left: 1pt solid rgb(189, 214, 238); border-image: initial; border-top: none; padding: 5.65pt 5.4pt;" valign="top" width="141">**<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">Automated,</span>**

**<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">user initiated via available issuer channel</span>**

</td><td style="width: 230.969px; border-top: none; border-left: none; border-bottom: 1pt solid rgb(189, 214, 238); border-right: 1pt solid rgb(189, 214, 238); padding: 5.65pt 5.4pt;" valign="top" width="95"><span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">Card credential and personal data are pushed automatically, after accepting T&amp;C’s by the user.</span>

</td><td style="width: 289.891px; border-top: none; border-left: none; border-bottom: 1pt solid rgb(189, 214, 238); border-right: 1pt solid rgb(189, 214, 238); padding: 5.65pt 5.4pt;" valign="top" width="161"><span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">Convenient flow, with experience similar to xPay push provisioning. Cardholder intentionally enrolls a card and is thus aware of possibility to use C2P.</span>

<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;"> </span>

**<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">Recommended implementation.</span>**

</td><td style="width: 166.438px; border-top: none; border-left: none; border-bottom: 1pt solid rgb(189, 214, 238); border-right: 1pt solid rgb(189, 214, 238); padding: 5.65pt 5.4pt;" valign="top" width="198"><span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;"><span style="mso-spacerun: yes;"> </span>Verestro TMP API </span>

<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">(including **Synchronous card enrollment endpoint**), </span>

<span lang="EN-US" style="color: #3d4a5c; mso-ansi-language: EN-US;">Visa SRC / MDES for Digital Commerce integration</span>

</td></tr><tr style="mso-yfti-irow: 1;"><td style="width: 156.688px; border-right: 1pt solid rgb(189, 214, 238); border-bottom: 1pt solid rgb(189, 214, 238); border-left: 1pt solid rgb(189, 214, 238); border-image: initial; border-top: none; padding: 5.65pt 5.4pt;" valign="top" width="141">**<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">Automated, </span>**

**<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">issuer initiated</span>**

</td><td style="width: 230.969px; border-top: none; border-left: none; border-bottom: 1pt solid rgb(189, 214, 238); border-right: 1pt solid rgb(189, 214, 238); padding: 5.65pt 5.4pt;" valign="top" width="95"><span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">Card credential and personal data are pushed automatically, without user additional engagement. C2P T&amp;C’s are usually part of issuer’s T&amp;C and consent is given during card activation.</span>

</td><td style="width: 289.891px; border-top: none; border-left: none; border-bottom: 1pt solid rgb(189, 214, 238); border-right: 1pt solid rgb(189, 214, 238); padding: 5.65pt 5.4pt;" valign="top" width="161"><span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">Very convenient flow, with minimal user engagement. Although it’s recommended by TSPs, cardholders may not be aware that their card has been pushed to C2P. This flow can also be used for card migrations and bulk enrollments.</span>

<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;"> </span>

<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;"> </span>

**<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">Recommended for migrations.</span>**

<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;"> </span>

</td><td style="width: 166.438px; border-top: none; border-left: none; border-bottom: 1pt solid rgb(189, 214, 238); border-right: 1pt solid rgb(189, 214, 238); padding: 5.65pt 5.4pt;" valign="top" width="198"><span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">Verestro TMP API </span>

<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">(including **Bulk card enrollment endpoint**),   
</span>

<span lang="EN-US" style="color: #3d4a5c; mso-ansi-language: EN-US;">Visa SRC / MDES for Digital Commerce integration</span>

</td></tr><tr style="mso-yfti-irow: 2;"><td style="width: 156.688px; border-right: 1pt solid rgb(189, 214, 238); border-bottom: 1pt solid rgb(189, 214, 238); border-left: 1pt solid rgb(189, 214, 238); border-image: initial; border-top: none; padding: 5.65pt 5.4pt;" valign="top" width="141"><span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">Manually, </span>

<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">via Merchant’s Payment Gateway</span>

</td><td style="width: 230.969px; border-top: none; border-left: none; border-bottom: 1pt solid rgb(189, 214, 238); border-right: 1pt solid rgb(189, 214, 238); padding: 5.65pt 5.4pt;" valign="top" width="95"><span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">Cardholder needs to manually type card credentials, personal data and accept T&amp;C’s during ecommerce payment.</span>

</td><td style="width: 289.891px; border-top: none; border-left: none; border-bottom: 1pt solid rgb(189, 214, 238); border-right: 1pt solid rgb(189, 214, 238); padding: 5.65pt 5.4pt;" valign="top" width="161"><span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">This flow requires significant friction and may result in cart abandonment. Convenient for issuers, as works out of the box, assuming MDES/VTS are integrated. Less popular with cardholders.</span>

</td><td style="width: 166.438px; border-top: none; border-left: none; border-bottom: 1pt solid rgb(189, 214, 238); border-right: 1pt solid rgb(189, 214, 238); padding: 5.65pt 5.4pt;" valign="top" width="198"><span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;"><span style="mso-spacerun: yes;"> </span>Verestro TMP API,</span>

<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;"><span style="mso-spacerun: yes;"> </span>VTS / MDES integration</span>

</td></tr><tr style="mso-yfti-irow: 3; mso-yfti-lastrow: yes;"><td style="width: 156.688px; border-right: 1pt solid rgb(189, 214, 238); border-bottom: 1pt solid rgb(189, 214, 238); border-left: 1pt solid rgb(189, 214, 238); border-image: initial; border-top: none; padding: 5.65pt 5.4pt;" valign="top" width="141"><span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">Manually, </span>

<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">via TSP website</span>

</td><td style="width: 230.969px; border-top: none; border-left: none; border-bottom: 1pt solid rgb(189, 214, 238); border-right: 1pt solid rgb(189, 214, 238); padding: 5.65pt 5.4pt;" valign="top" width="95"><span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">Cardholder needs to register to click to pay via TSP website and manually type card credentials, personal data and accept T&amp;C’s.</span>

</td><td style="width: 289.891px; border-top: none; border-left: none; border-bottom: 1pt solid rgb(189, 214, 238); border-right: 1pt solid rgb(189, 214, 238); padding: 5.65pt 5.4pt;" valign="top" width="161"><span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">This flow requires not only a lot of effort from the cardholder, but also knowledge about existence of such websites. Convenient for issuers, as works out of the box, assuming MDES/VTS are integrated. Least popular with cardholders.</span>

</td><td style="width: 166.438px; border-top: none; border-left: none; border-bottom: 1pt solid rgb(189, 214, 238); border-right: 1pt solid rgb(189, 214, 238); padding: 5.65pt 5.4pt;" valign="top" width="198"><span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">Verestro TMP API, </span>

<span lang="EN-US" style="font-size: 10.0pt; color: #3d4a5c; mso-ansi-language: EN-US;">VTS / MDES integration</span>

</td></tr></tbody></table>

### The Token Management Platform as the Issuer's API Gateway

<span lang="EN-US" style="color: #3d4a5c; mso-ansi-language: EN-US;">Rather than integrating directly with Visa SRC and Mastercard MDES APIs separately — each with distinct authentication, schemas, and lifecycle models — the issuer connects to a single Token Management Platform. The TMP normalises both networks behind a unified REST API, handles routing to the correct SRCS based on card BIN, manages token lifecycle and provides reporting.</span>