
Key features and benefits
- Ease of Use: It enables consumers to make online purchases with a single click, eliminating the need to enter credit card details for each purchase manually.
- Enhanced Security: Utilizes modern authentication standards to minimize fraud risk. This may include methods such as two-factor authentication or payment tokens.
- Consistent Across Various Sites: Offers a similar payment experience across all websites that support this technology, meaning consumers don’t have to learn different processes for each online store.
- Integration with Card Brands: Being backed by major card brands, “Click to Pay” is widely accepted and trusted.
- Mobile and Desktop Compatibility: Designed to work across various devices, it facilitates online shopping on both desktops and mobile devices.
Integration
To integrate and start offering Click to Pay to your customers, follow these 4 simple steps:-
Create a connection in the Yuno dashboard using your Click to Pay credentials.

-
Define the payment method route in the Routing section in order to be able to enable it in the Checkout Builder.

-
Enable Click to Pay in the Checkout builder.

- Define the Card route: Taking in consideration that Click to Pay is a wallet that stores credit card information, the route where you will need to define the providers for each scenario is the same as the ‘Card’ payment method.
VTEX integration
For VTEX merchants using Click to Pay, the integration provides automatic customer creation and data mapping to streamline the checkout experience. Automatic customer creation: When customers choose Click to Pay on VTEX stores:- The VTEX customer is automatically created in Yuno during payment initialization (if not already existing)
- All customer data from the VTEX profile is automatically mapped to Yuno and included in the checkout session
- Customer information (CVV, email, address) is pre-filled in the SDK, eliminating redundant data entry
- The checkout flow matches the streamlined experience available for non-VTEX merchants
SDK integration (Click to Pay Passkey)
ImportantStandard Click to Pay card flows use the existing SDK callbacks, but Passkey users must include a For Passkey transactions, the one-time token (OTT) never reaches the usual SDK callbacks (including
callback_url that matches the app’s deeplink scheme so the shopper returns to the app after authentication (on Android this must match the scheme configured in AndroidManifest.xml). For example:callbackOTT on Android). Always read it from the deeplink parameters before continuing the flow.iOS Passkey flow
The Yuno iOS SDK supports Click to Pay with Passkey. The flow differs from standard card payments because the SDK returns the result by deeplink instead of via the usual delegate callbacks.Handle the one-time token (OTT) and deeplink
When a shopper completes the Click to Pay Passkey flow, the SDK sends the result through the deeplink URL instead of theyunoCreatePayment(with token: String) delegate method.
1. Close the external browser
When your app receives the deeplink callback, immediately callYuno.receiveDeeplink to let the SDK dismiss the external browser that was used for Passkey authentication.
2. Process the deeplink URL
The deeplink query string includes the information you need to continue:has_error: Indicates an error occurred during the transaction. Handle this scenario in your app.one_time_token: Present when the transaction succeeds. Use it to create the payment.
3. Create the payment
If the deeplink contains aone_time_token:
- Extract the
one_time_token. - Use it to create the payment with the Create Payment endpoint.
- After creating the payment, call
continuePaymentin the SDK to finalize the flow.
ImportantThe OTT never reaches
yunoCreatePayment(with token: String) for Click to Pay Passkey. Always read the token from the deeplink URL.Android Passkey flow
For Android, include acallback_url that matches your app’s deeplink scheme when creating the checkout session, add the corresponding intent-filter in AndroidManifest.xml, and handle the deeplink in both onCreate and onNewIntent. When the deeplink arrives:
- Check
has_errorto manage cancellations or failures. - Extract
one_time_token(and the optionalcheckout_session) from the URI. - Send the OTT to your backend to call the Create Payment endpoint, then invoke
continuePaymentin the SDK to resume the flow.