# Click to Pay Direct API Token Passthrough
source: https://developer.mastercard.com/mastercard-gateway/documentation/gateway-features/click-to-pay/c-t-p-direct-api-token-pass/index.md

## Overview {#overview}

Click to Pay is an intelligent, password-free online checkout option that provides a quick and easy checkout experience designed to make 'guest checkout' faster and easier across all devices.

Click to Pay provides a single checkout button and a standardized checkout flow for all participating card schemes, including Mastercard, Visa, American Express, Discover, and others.

Click to Pay uses EMVCo's Secure Remote Commerce (SRC) specification and replaces Masterpass, Visa Checkout, and Amex Express Checkout.

A payer can create a Click to Pay profile using their email address. During checkout, the payer must then provide this email address and perform an additional verification step with a one-time passcode (OTP). They can also choose the "Remember me" option to skip the verification when using the same browser in a subsequent checkout.

The payer can store these details in their Click to Pay profile:

* Multiple credit cards
* Multiple debit cards
* Multiple prepaid cards
* Associated billing addresses
* Multiple shipping addresses

The system securely stores card details and provides additional protection by using network tokenization whenever possible if you enable the market enables acceptance of network tokenization.

Click to Pay lets your payer choose which payment details to use; however, the gateway processes the payment using the acquirer configured for your merchant profile.

You need to build your integration using the MTF environment first and then go live in the production environment.

## Key benefits {#key-benefits}

Click to Pay offers the following benefits:

* Intelligent consumer recognition, 'embedded' into the checkout flow, to initiate faster guest checkout across all devices (with no passwords to remember).
* A reduction in clicks and manual card entry to increase conversion and create frictionless experiences.
* Potential for higher authorization approval rates, through network tokenization, assisting in the reduction of preventable declines.
* Built upon EMVCo Secure Remote Commerce standards to create a consistent user experience and lower fraud rates in e-commerce guest checkout payment moments.
* Secure exchange of payment data including card details, billing, and shipping address details

## Prerequisites {#prerequisites}

Note: Integrated with Mastercard Gateway API version 57 and later.

If you want to offer Click to Pay as a checkout option to your payers:

* Work with the Click to Pay team to onboard to Mastercard SRCi.
* If using Scheme tokens over FPANS, work with the Click to Pay team to ensure Mastercard SRCi provides them.
  * If using FPANs, work with the Click to Pay team to ensure Mastercard SRCi provides them. Then, see the Send the Transaction Request page for the steps required to process FPANs.

## Click to Pay Integration Contact Information {#click-to-pay-integration-contact-information}

* [Integration guide](https://developer.mastercard.com/unified-checkout-solutions/documentation/) for Mastercard SRCi
* [Support page](https://developer.mastercard.com/unified-checkout-solutions/documentation/support/) for Mastercard SRCi

## Perform payment operation {#perform-payment-operation}

### Token payments {#token-payments}

When you integrate directly with the network Token Service Provider, you must obtain the token details from the provider, and provide these details to the gateway on an Authorization/Pay request to process payments.

### Transaction request {#transaction-request}

In addition to the standard fields, provide the following fields in an Authorization or Pay request to process payments using network tokens issued by the network tokenization service providers.

* `walletProvider`=SECURE_REMOTE_COMMERCE:Details about the source of the payment used for digital payment methods.
* `type`=SCHEME_TOKEN:Enables the gateway to identify the source of fund provided in the request as a network token.
* `provided.card.number`: The network token.
* `provided.card.expiry`: The network token expiry.
* `provided.card.devicePayment.onlinePaymentCryptogram`: Use the cryptogram directly from the decrypted transaction credentials.
* `provided.card.devicePayment.eciIndicator`=07:The Electronic Commerce Indicator.
* `provided.card.securityCode`: The token verification code if issued by the tokenization service.
* `source`=INTERNET:Indicates the channel through which you received authorization for the payment for this order from the payer.

### Transaction response {#transaction-response}

When the Authorization or Pay request includes a network token, the Retrieve Transaction response returns the following.

* `type`=SCHEME_TOKEN- if a network token is used in the Authorization or Pay transaction.

If the acquirer returns an FPAN

* `provided.card.number`: The masked FPAN (Funding PAN).
* `provided.card.expiry`: The FPAN expiry.
* `provided.card.deviceSpecificNumber`: The network token from MDES ("Token PAN") or VTS ("Token") or AETS ("Token").
* `provided.card.deviceSpecificExpiry`: The network token expiry.

If the acquirer does not return an FPAN:

* `provided.card.number`: The fully masked value.
* `provided.card.deviceSpecificNumber`: The network token from MDES ("Token PAN") or VTS ("Token") or AETS ("Token").
* `provided.card.deviceSpecificExpiry`: The network token expiry.

## Testing details {#testing-details}

### Supported testing methods {#supported-testing-methods}

Due to the complexity with the Token Passthrough method, merchants must currently test with their LIVE Production merchant.

|   Region   | Live or Test Merchant? |                                                                        Card Type Used                                                                         |                                         Functionality/Purpose                                         |
|------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|
| MTF        | Live                   | [Click to Pay Provided -- Sandbox Test Card](https://developer.mastercard.com/unified-checkout-solutions/documentation/testing/test_cases/click_to_pay_case/) | You can integrate with the Mastercard SRCi Sandbox environment to test the flow of Token Passthrough. |
| Production | Live                   | Live cards owned by the merchant                                                                                                                              | Full end to end testing with Mastercard Gateway and Click to Pay Token Passthrough method.            |