# Repeat Click to Pay User on Recognized Device Guide source: https://developer.mastercard.com/mastercard-checkout-solutions/documentation/tutorials-and-guides/returninguser-recognized-ui-tutorial/index.md Click to Pay users, during their checkout journey, can encounter different checkout screens. Note: Consumers get the loading screen as the default Digital Card Facilitator (DCF) experience. For detailed integration steps, see [Repeat User on Recognized Device](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/use-cases/click-to-pay/returninguser_recognized/index.md). ## Mastercard's DCF Screen {#mastercards-dcf-screen} The Mastercard DCF screen varies based on a combination of factors passed in the in [init()](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/init/index.md) or [checkoutWithCard()](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/checkout-method/index.md) methods. | Parameter | Details | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [customInputData](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/common-objects/index.md#custom-input-data) | Card enrollment options presented by Mastercard DCF: * `WITHIN_CHECKOUT` - This experience offers Click to Pay as a payment option to complete Checkout for an order. * `PAYMENT_SETTINGS` - This experience offers Click to Pay to enroll and add their cards for faster checkout. | | [confirmPayment](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/common-objects/index.md#dpa-transaction-options) | If explicitly set to `True`, Mastercard DCF prompts the consumer to confirm the payment before completing checkout. | | [dpaBillingPreference](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/common-objects/index.md#dpa-transaction-options) | Possible values are `FULL`/`POSTAL_COUNTRY`/`NONE` that impact the behavior of the DCF screen. | | [consumerEmailAddressRequested](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/common-objects/index.md#dpa-transaction-options) or [consumerPhoneNumberRequested](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/common-objects/index.md#dpa-transaction-options) or [consumerNameRequested](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/common-objects/index.md#dpa-transaction-options) | If consumer name, email address or mobile number are not passed in the checkout payload, DCF screen prompts consumer to enter them. | ## Scenario 1: Order Review with 'DCF payment sheet' {#scenario-1-order-review-with-dcf-payment-sheet} In this scenario, if an integrator does not have an order review screen at their end, consumers must explicitly confirm payment within the Mastercard DCF Payment Sheet. ![Returning consumer on a repeated device](https://static.developer.mastercard.com/content/mastercard-checkout-solutions/documentation/tutorials-and-guides/ui-guide/img/rur-img/scenario-1.png "Returning Consumer on a returning device ") * Once the user is recognized on the device using the [isRecognized()](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/is-recognized/index.md) method, card is shown in the list on the payment page. * User selects a card for payment. Integrator initiates the [checkout()](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/checkout-method/index.md) method. * Since the integrator does not have an order review screen, Mastercard DCF prompts the consumer to review the payment information. * Once the consumer continues, Mastercard DCF secures the payment information and redirects the consumer back to the integrator. > **Integration Notes** > > This experience occurs when SRCi passes: > > * Either `PAYMENT_SETTINGS` OR `WITHIN_CHECKOUT` enum values as part of [customInputData](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/common-objects/index.md#custom-input-data). > AND > * [confirmPayment](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/common-objects/index.md#dpa-transaction-options) as `TRUE`. ## Scenario 2: Prompt to Add Missing Profile Data {#scenario-2-prompt-to-add-missing-profile-data} If an existing consumer profile does not have full billing address or first and last name associated to the card chosen for the checkout, present Mastercard DCF screen to collect the billing address for that card. ![Returning consumer on a repeated device-1](https://static.developer.mastercard.com/content/mastercard-checkout-solutions/documentation/tutorials-and-guides/ui-guide/img/rur-img/scenario-2.1.png "Returning Consumer on a repeated device WHEN INTEGRATOR REQUESTED DATA IS NOT AVAILABLE IN PROFILE") ![Returning consumer on a repeated device](https://static.developer.mastercard.com/content/mastercard-checkout-solutions/documentation/tutorials-and-guides/ui-guide/img/ruu-img/2.png "Returning Consumer on a repeated device WHEN SRCi REQUESTED DATA IS NOT AVAILABLE IN PROFILE") * Present Mastercard DCF as a loading screen to indicate that the payment is being securely processed by the Mastercard network and redirect consumer back to the integrator. * Consumer is prompted to add missing profile details.
> **Integration Notes** > > This experience occurs when integrator passes: > > * Either `PAYMENT_SETTINGS` OR `WITHIN_CHECKOUT` enum values as part of [customInputData](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/common-objects/index.md#custom-input-data). > AND > * [dpaBillingPreference](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/common-objects/index.md#dpa-transaction-options) as `FULL` OR `POSTAL_COUNTRY` but entire billing address data is not available in consumer profile. > OR > * [consumerNameRequested](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/sdk-reference/common-objects/index.md#dpa-transaction-options) as `TRUE` but data is not available in consumer profile stored in SRC network.