Shoppers with Click to Pay accounts are recognized during checkout and can select their preferred card details from their Click to Pay account to complete the payment.<\/p>\n
Currently, Adyen's Click to Pay integration doesn't support recurring payments<\/a>, meaning you can't offer it for subscriptions and automatic top-ups. To offer recurring payments, use our regular Card<\/a> Component or Drop-in instead.<\/p>\n<\/div>\n The requirements for Click to Pay differ depending on your integration. Select the tab corresponding to your integration:<\/p>\n\n Click to Pay offers the following benefits:<\/p>\n To offer this flow, you need to:<\/p>\n The following image represents Adyen's implementation of Visa and Mastercard brand guidelines for a Click to Pay checkout page. We recommend you offer Click to Pay through Adyen's Web Drop-in or Component integration, because it meets card scheme requirements.<\/p>\n If you do not use Adyen's provided component, you must follow EMVCO customer experience guidelines<\/a> to build your Click to Pay checkout component.<\/p>\n How you configure Click to Pay depends on your integration:<\/p>\n Adyen does not support a custom pay button for Click to Pay. You must use the button provided by the Component.<\/p>\n<\/div>\n Your integration recognizes an existing Click to Pay user by the cookie stored in their browser. If there is no cookie, the user will be prompted to authenticate with their email address, which will set a new cookie.<\/p>\n When Click to Pay recognizes the shopper, the Card Component or Drop-in shows the Click to Pay payment option.<\/p>\n If the shopper is using a Mastercard but there is no browser cookie, the console always returns a 400 Bad Request error<\/a>. This occurs even when the payment flow continues successfully. As long as the shopper's email is registered, you can continue the payment flow.<\/p>\n<\/div>\n To recognize whether a Click to Pay account is registered with your shopper's email address:<\/p>\n A payment request with Click to Pay sends the same parameters as a standard cards<\/a> request, plus the following parameters in the Click to Pay requests also include a When you receive a payment response, the To test Click to Pay:<\/p>\n Add test cards to your account:<\/p>\n For Visa, use any of the following cards:<\/p>\nRequirements<\/h2>\n
Benefits<\/h2>\n
\n
How it works<\/h2>\n
\n
\nThis step is skipped if the shopper is using a recognized device.<\/li>\n\n
Checkout example<\/h3>\n
![\"Click](\"\/user\/pages\/docs\/08.payment-methods\/04.cards\/23.click-to-pay\/clicktopay.png\" "\\"Click")
1. Configure your integration<\/h2>\n
\n
2. Recognize the Click to Pay user<\/h2>\n
\n
\/sessions<\/code> response to your AdyenCheckout<\/code> configuration<\/a>.<\/li>\nshopperEmail<\/code> to the card configuration.<\/li>\n<\/ul>\n\nSample request and response<\/h2>\n
Payment request<\/h3>\n
paymentMethod<\/code> object:<\/p>\n\n
srcDigitalCardId<\/code>: The SRC<\/a> reference for the Click to Pay token.<\/li>\nsrcCorrelationId<\/code>: An identifier used for the Click to Pay transaction.<\/li>\n<\/ul>\nconfiguration<\/code> object that automatically sends the following parameters that identify your CTP accounts or storefronts with the schemes:<\/p>\n\n
mcDpaId<\/code><\/li>\nmcSrcClientId<\/code><\/li>\nvisaSrcInitiatorId<\/code><\/li>\nvisaSrciDpaId<\/code><\/li>\n<\/ul>\n\nPayment response<\/h3>\n
paymentMethod<\/code> object contains:<\/p>\n\n
paymentMethod.type<\/code> is scheme<\/strong><\/span>.
\nPossible values are mc_clicktopay<\/strong><\/span> and visa_clicktopay<\/strong><\/span>.<\/li>\n<\/ul>\nTest and go live<\/h2>\n
\n
\n
\n
![\"\"](\"https:\/\/docs.adyen.com\/user\/pages\/docs\/08.payment-methods\/04.cards\/23.click-to-pay\/clicktopay.png\")
"}}