On This Page

Features

Unified Checkout
 comprises these features.
Save Card
This feature enables you to display a consent option in the
Unified Checkout
 UI for the cardholder to save their payment details for future use. If you use the complete mandate to create a token, see Capture Context API.
When you use this field without using the complete mandate, the transient token payload includes the
consumerPreference.saveCard
 field with the value set to
true
 when the cardholder has checked to save the payment information for future purchases: 
"captureMandate" : {
      "requestSaveCard": true
}
Combo Cards
A combo card is a single card in Brazil that functions as both a debit and a credit card.
Unified Checkout
 enables the cardholder to choose whether to pay for a transaction using a debit or credit card. The cardholder can choose the card that they want to use when they enter their card details or when they choose a stored Visa card from their
Click to Pay
 wallet during checkout. While in the card details section of the payment form, the cardholder is prompted for a debit or credit card. Credit is the default option.
To enable combo cards during checkout, you must include the
comboCard
 field in your capture context request and set the field value to
true
. When the
comboCard
 field value is set to
true
, the option to use a debit or credit card appears for all Visa cards that are entered in
Unified Checkout
 and for all cards that are already stored in
Click to Pay
. If you do not want to offer a combo card at checkout, do not include the
comboCard
 field in your capture context request:
"captureMandate" : {
      "comboCard": true
}
Cadastro de Pessoas Físicas (CPF) – Brazilian Tax ID
The tax ID feature is for customers in Brazil and provides your customers with a way to include their Consumer National Identifier when it is requested at checkout. Include this field in the capture context to display this field within the flow for manual card entry and
Click to Pay
 transactions:
"captureMandate" : {
    "CPF": {
        "required": true
    }
}
Email Autolookup
When you include
Click to Pay
 as an
allowedPaymentType
, an automatic email lookup occurs when an email address is included in the capture context request. If the user has a
Click to Pay
 account but is not on a recognized device, a one-time password (OTP) screen appears and the user is prompted to enter their OTP. If the user does not have a
Click to Pay
 account, the user must enter their card information manually. They will have the option to create a
Click to Pay
 account.
To enable email autolookup, you must include
CLICKTOPAY
 as a value in the
allowedPaymentTypes
 field and include an email address in the capture context.
Removal of Confirm and Continue Screen
When
showConfirmstionStep
 is set to
false
, you can remove the final summary confirmation screens from the checkout experience. When the UI displays cardholder data, the cardholder can review and, if necessary, edit their payment details before checkout is complete. 
{
  "captureMandate": {
    "showConfirmationStep": false
  }
}
Click to Pay
 Enrollment Pre-Check
You can have the
Click to Pay
 box pre-checked when a user is manually entering their card details and
Click to Pay
 is enabled. The customer can uncheck the box if necessary, which means the request is processed as a one-time manual PAN transaction. This is available when you set the
billingType
 field to
PARTIAL
 or
FULL
 in the capture context. This ensures that the customer's billing country can be validated in the UI.
Click to Pay
 enrollment pre-check is available in these countries:
  • Argentina
  • Brazil
  • Chile
  • Colombia
  • Kuwait
  • Mexico
  • Peru
  • Qatar
  • Saudi Arabia
  • South Africa
  • Ukraine
  • United Arab Emirates
{
  "allowedPaymentTypes": [
    "PANENTRY",
    "GOOGLEPAY",
    {
      "type": "CLICKTOPAY",
      "options": {
        "autoCheckEnrollment": true
      }
    },
    "APPLEPAY",
    "PAZE"
  ]
}
Unified Checkout
 Checkout Button Name
When
Unified Checkout
 loads, the payment buttons displayed are based on what you include in the
allowedPaymentTypes
 object in the capture context.
Unified Checkout
 enables you to customize the text on the payment buttons. You can do this by setting the
buttonType
 field object in the capture context to one of these values:
  • ADD_CARD
  • CARD_PAYMENT
  • CHECKOUT_AND_CONTINUE
  • DEBIT_CREDIT
  • DONATE
  • PAY
  • PAY_WITH_CARD
  • SUBSCRIBE_WITH_CARD
If you do not include the
buttonType
 field in your request, the payment button text defaults to
Checkout with card
. For example:
RELATED TO THIS PAGE