On This Page

{#jumplink-list}  
[Markdown](/docs/cybs/en-us/digital-accept-flex/developer/all/rest/digital-accept-flex/ctp-intro/ctp-setup-capture-context/ctp-capture-context-features.md)  
Filter  
FILTER BY TAG

Features {#uc-capture-context-features}
=======================================

This section includes information on the features that are supported in `Click to Pay`.

Save Card
:
This feature enables you to display an option in the `Unified Checkout` UI for the cardholder to save their payment details for future use. IMPORTANT
> This feature is available only for card credentials that are manually entered during checkout. If ` Click to Pay ` is an available payment method, do **not** select *Save this card with ` Click to Pay `*.

    When the customer selects the checkbox and finalizes their purchase, you receive a notification in the transient token response to your capture context request. The transient token payload includes the consumerPreference.saveCard field value set to `true` when the cardholder selects the option to save their card:

    ```
    "captureMandate": {
        "requestSaveCard": true
      }
    ```

Email Autolookup
:
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 and 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.

Mobile as Identity for `Click to Pay`
:
`Click to Pay` supports mobile numbers as way to identify a user. This enables cardholders to use their mobile number instead of their email address in certain markets for Visa and Mastercard transactions.
:
When the requestEmail field is set to `false` and the requestPhone field is set to `true`, the cardholder is identified using the provided mobile number. When the requestEmail field is set to `true` and the requestPhone field is set to `false`, the cardholder is identified using the provided email address. When the requestEmail field is set to `true` and the requestPhone field is also set to `true`, the cardholder is identified using the provided email address first and then the mobile number if there is no match.

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"
      ]
    }
    ```

Checkout Button Name
:
When `Click to Pay Drop-In UI` loads, the payment buttons displayed are based on what you include in the allowedPaymentTypes object in the capture context. You can customize the text on the payment buttons 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:

![](/content/dam/new-documentation/documentation/en-us/topics/payments-processing/card-processing/click-to-pay/images/ctp-300x100.svg/jcr:content/renditions/original)  
\]

Features Available in Brazil
----------------------------

These features are available only in Brazil:

Combo Cards
:
A combo card is a single card that functions as both a debit and a credit card. `Click to Pay` enables the cardholder to choose whether to pay for a transaction using a debit or credit card. The cardholder can select the card type that they want to use when checking out with Visa cards. While in the card details section of the payment form, the cardholder is prompted to decide if they would like to pay using a debit or credit card. Credit is selected as the default option.  
> IMPORTANT Combo cards are applicable only for issuers that are located in Brazil.

    To enable combo cards during checkout, you must include the comboCard field in your capture context request and set the field value to `true`:

    ```
    "captureMandate": {
        "comboCard": 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 `Click to Pay` and for all cards that are already stored in `Click to Pay`. If you do not want to offer combo card at checkout, do not include the comboCard field in your capture context request.

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
        }
    }
    ```


    > IMPORTANT This feature is required for customers in Brazil.

RELATED TO THIS PAGE