Click to Pay

New User Registration

The Shopper clicks on the 'Click to Pay' checkbox on the Card widget and completes the Payment. On the click of this checkbox, Click to Pay workflow is triggered. When the payment is confirmed, TF (Token Fetch) is created. TF retrieves the Account Data from the Scheme based on the RIRO Configuration at Administration > Processing > Click to Pay Configuration. It can be Full PAN or DPAN (for Network Tokens). Once TF is completed, actual payment transaction(PA/DB) is created which goes to the Acquirer.

How it works

Capture the Card Details

Shopper enters the Card Details and clicks 'Click to Pay' checkbox on the Card widget.

Create the new 'Click to Pay' profile

The Shopper proceeds for the Checkout on the Merchant's website and opts to pay via Credit Card. They will enter their Card details and will agree to register for 'Click to Pay' using the Checkbox on the card widget. The Shopper is then directed to the Scheme's page while doing the payment where they share their information like Name, Address, Contact Number to create their Click to Pay profile. Profile gets created when the payment is completed.

Payment Response

Based on the configuration settings, Scheme returns Email ID, Mobile Number, Address of the Shopper and their masked Account details. If the Dynamic Data type settings indicate that the Scheme returns the Full Card details, then masked Credit card data is retrieved. If the Dynamic Data type settings indicate that the Scheme returns the Token details, then masked Network Token data is retrieved like Token Account Number, Expiry and Cryptogram. Once the Token Fetch is completed and the account data is retrieved from the Scheme , actual payment is created (PA/DB) which goes to the Acquirer.

Cookie Recognition

The Shopper with an existing account with the Merchant proceeds for the Checkout on the Merchant's website. On selecting the Credit Card as the Payment Option, they get recognized by the Browser Cookies since they are the returning shopper and already registered for Click to Pay. After the successful recognition, the Shopper is presented with the list of Click to Pay- registered cards. They select a card from the list, review and make the payment. This Use case allows the Shopper to pay without any manual card entry.

How it works

Choose to pay via Credit Card

The Recognized Shopper is presented with the list of cards registered against their Click to Pay profile.

Returning Shopper gets recognized via Cookies

The Recognized Shopper is presented with the list of cards registered against their Click to Pay profile when they choose to pay via Credit Card. Scheme Library recognizes the Returning Shopper based on the Browser Cookies and present them the list of cards registered against their Click to Pay profile.

Payment Response

Based on the configuration settings, the Scheme returns Email ID, Mobile Number, Address of the Shopper and their masked Account details. If the Dynamic Data type settings indicate that the Scheme returns the Full Card details, then masked Credit card data is retrieved. If the Dynamic Data type settings indicate that the Scheme returns the Token details, then masked Network Token data is retrieved like Token Account Number, Expiry and Cryptogram. Once the Token Fetch is completed and the account data is retrieved from the Scheme, actual payment is created (PA/DB) which goes to the Acquirer.

Email ID Lookup

The Shopper with an existing account with the Merchant proceeds for the Checkout on the Merchant's website. On selecting the Credit Card as the Payment Option, they can enter their Email ID. If the Shopper is Registered for Click to Pay, an OTP is triggered to their Mobile Number/Email address. After the successful recognition, the Shopper is presented with the list of Click to Pay- registered cards. They select a card from the list, review and make the payment. This Use case allows the Shopper to pay without any manual card entry.

How it works

Shopper enters the Email address after opting to pay via Credit Card

Shopper opts to pay via Credit Card and they enter their Email Address. the Scheme Library gets called to check if that email is enrolled for Click to Pay. If the email address is registered for Click to Pay, Shopper is requested to enter an OTP triggered on their phone/email. Once the authentication is successful, shopper is presented with the list of cards against their registered Click to Pay profile.

Email ID lookup

To check if the email provided by the Shopper is registered for Click to Pay, the Scheme Library is called. If the profile is found, OTP authentication is triggered which when successful, returns the Card list registered against that Click to Pay profile.

Payment response

Based on the configuration settings, the Scheme returns Email ID, Mobile Number, Address of the Shopper and their masked Account details. If the Dynamic Data type settings indicate that the Scheme returns the Full Card details, then masked Credit card data is retrieved. If the Dynamic Data type settings indicate that the Scheme returns the Token details, then masked Network Token data is retrieved like Token Account Number, Expiry and Cryptogram.

External Tokens

Consider you accept payments through an acquirer that generates its own tokens. External Tokens allow you to securely process payments and store tokens for future transactions with the same acquirer.

Benefits

• Enhances Security: Uses tokens generated by trusted acquirers, reducing the risk of data breaches.
• Simplifies Payment Processing: Streamlines transactions with specific acquirers.
• Flexible Token Storage: Tailored to your business needs, allowing for various storage options.

Example

When a customer makes a purchase through your store, an External Token is generated. This token can be stored and used for future transactions with Square, ensuring secure and efficient payment processing.

ApplePay Tokens

Imagine you run an online store that caters to a large number of Apple device users. Apple Pay Merchant Tokens (MPANs) securely link your customers’ payment cards to your business through their Apple Wallet. By using MPANs, you can offer a seamless payment experience that works across multiple devices and supports recurring transactions without being tied to any single device. This ensures that even if your customers change or lose their devices, their payment information remains accessible and secure.

Key Benefits of Using MPANs

• Multi-device continuity: Hassle-free payments across all devices.
• Device-independent recurring payments: Perfect for subscriptions or regular purchases.
• Persistent payment information: Safeguards against device loss or theft.
• Lifecycle management tools: Track token activity and revocation status.

Additional Benefits

• Enhanced Security: Apple Pay tokens replace sensitive card details with secure tokens, reducing the risk of unauthorized use. Each transaction is authorized with a one-time unique dynamic security code.
• Improved Customer Experience: Apple Pay tokens streamline the checkout process for Apple device users, allowing them to complete purchases quickly and easily using Face ID, Touch ID, or their device passcode.
• Increased Trust: Customers are more likely to trust and use a payment method that is known for its security and ease of use, potentially increasing your sales.

Types MPAN Requests

• Automatic Reload: For automatic top-ups, like adding funds to a store card.
• Recurring Payment: For subscriptions, such as monthly streaming services.
• Deferred Payment: For future payments, like booking a hotel room.

How to Get an MPAN

Follow our guidelines here. Ensure your card issuer supports MPAN generation.

Example

A customer shopping on your online store using their iPhone can use Apple Pay to complete their purchase with just a touch or a glance. The Apple Pay token ensures that their card details are never shared with the merchant, providing a secure and convenient payment experience.