# Merchant Embedded Native Experience source: https://developer.mastercard.com/masterpass-merchant-integration-v7/documentation/merchant-embedded-native-experience/index.md The Merchant embedded native experience is an enhancement to the Masterpass mobile SDKs which provides Masterpass registration, sign-in and checkout from within a Merchant's mobile app using native screens. To use the native embedded experience in your app, you will need to use at least the following versions of the Masterpass mobile SDKs to build your app (the latest version is preferred): * iOS - minimum version 2.4 * Android - minimum version 2.4 * Cordova - not yet supported Apps built using earlier versions of the Masterpass SDKs will not use the native experience but will continue to work as normal. Apps built using the above versions of the SDK or newer will present the native experience to users in countries which support it. The native embedded experience is currently available in: * Brazil (Portugese) * Mexico (Spanish) * Canada (English and French) * India (English) * Thailand (English) * Argentina (Spanish) * Colombia (Spanish) * Hong Kong (English) * Singapore (English) * Philippines (English) * Malaysia (English) * Australia (English) * New Zealand (English) The SDK will communicate with the Masterpass server based on the locale set in the SDK configuration object that you create when your app initializes the SDK. As new countries are added apps which are enabled for the new experience will automatically present the new UI when the Masterpass server in each country is updated - no further update to the mobile app itself will be needed. Note: Mastercard offers consumers the ability to register or sign-in to a Masterpass wallet from within the app when no other wallet application is present on the consumer's device. ## Benefits {#benefits} The Merchant embedded native experience offers the following advantages:. * Seamless and frictionless consumer registration and checkout. * The consumer is not diverted outside the Merchant application. These benefits should increase repeat use. ## Consumer Flows {#consumer-flows} The section describes the primary consumer flows available with the new native experience. There are three primary flows: * Registration and Checkout * Un-recognized Checkout * Recognized Checkout These flows are described below. ### Registration and Checkout {#registration-and-checkout} The registration flow is used to create a Masterpass wallet account in the Merchant application. The consumer creates an account by supplying their personal information and card details. Consumers can also add a shipping address when purchasing physical goods. Finally, the consumer can complete checkout using the newly added card. #### Pre-Conditions {#pre-conditions} * The Merchant application is Masterpass enabled. #### Flow {#flow} The full flow is as follows: 1. The consumer launches the Merchant mobile app. 2. The consumer adds items to a shopping cart. 3. The consumer proceeds to checkout. 4. The consumer is shown a Masterpass button which they tap to proceed. 5. The consumer adds personal information. 6. The consumer adds a card for payment. 7. The consumer must accept the Masterpass terms and conditions before completing the registration process. 8. The consumer completes checkout. Note: * If the merchant is enabled for Express Checkout, consumers can pair their Masterpass wallet with their Merchant profile for even faster checkout. Refer to the [Merchant integration documentation](https://developer.mastercard.com/masterpass-merchant-integration-v7/documentation/web-integration/#standard-checkout) for more information on Express Checkout. * Masterpass terms and conditions will open in web view (native screens are not supported). ![alt text](https://static.developer.mastercard.com/content/masterpass-merchant-integration-v7/documentation/images/registration.jpg "MEX Registration") ### Unrecognized Sign-in and Checkout {#unrecognized-sign-in-and-checkout} The un-recognized checkout flow is triggered if the consumer has not previously signed in and successfully completed Masterpass checkout on this device. #### Pre-Conditions {#pre-conditions-1} * The Merchant application is Masterpass enabled. * The consumer has previously created a Masterpass wallet account. #### Flow {#flow-1} 1. The consumer launches the Merchant mobile app. 2. The consumer adds items to the shopping cart. 3. The consumer proceeds to checkout. 4. The consumer is shown a Masterpass button which they tap to proceed. 5. The consumer logs in to their Masterpas wallet using their credentials (email / mobile number and password). 6. The consumer will receive a One Time Password (OTP) for further authentication. 7. When the OTP is confirmed, the consumer is shown the card and shipping address (where enabled) selection screen. 8. The consumer completes checkout. Note: If the merchant is enabled for Express Checkout, consumers can pair their Masterpass wallet with their Merchant profile for even faster checkout. Refer to the [Merchant integration documentation](https://developer.mastercard.com/masterpass-merchant-integration-v7/documentation/) for more information on Express Checkout. ![alt text](https://static.developer.mastercard.com/content/masterpass-merchant-integration-v7/documentation/images/sign-in.jpg "MEX Unrecognized Checkout") ### Recognized Checkout {#recognized-checkout} The recognized checkout flow is only triggered after the consumer has previously signed in and successfully completed the un-recognized checkout flow on this device. This flow allows the consumer to skip the authentication step. #### Pre-Conditions {#pre-conditions-2} * The Merchant application is Masterpass enabled. * The consumer has previously successfully completed sign-in and checkout using Masterpass on this device. * Express Checkout is not enabled for this Merchant. #### Flow {#flow-2} 1. The consumer launches the Merchant mobile app. 2. The consumer adds items to the shopping cart. 3. The consumer proceeds to checkout. 4. The consumer is shown a Masterpass button which they tap to proceed. 5. The consumer is routed to the confirmation screen. The last used card and shipping address (if enabled by the Merchant) are pre-selected. The consumer has the option to select a different card from their Masterpass wallet account or add a new card. 6. The consumer completes checkout using the selected card. ![alt text](https://static.developer.mastercard.com/content/masterpass-merchant-integration-v7/documentation/images/recognized.jpg "MEX Recognized Flow") ### Fingerprint Recognition {#fingerprint-recognition} This section describes the use of biometrics in the Masterpass Merchant embedded native experience. As part of the release, Mastercard has introduced fingerprint recognition as an authentication and authorization mechanism in the checkout flows. Consumers can now access their Masterpass wallet and complete checkout with just a fingerprint. This feature is supported for iOS and Android. Note: FaceID is supported instead of fingerprint recognition for the iphone X from version 2.4.0 onwards of the Masterpass Checkout iOS SDK. #### Registration {#registration} The following diagram shows the use of fingerprint recognition during the Masterpass wallet account registration flow. ![alt text](https://static.developer.mastercard.com/content/masterpass-merchant-integration-v7/documentation/images/registration.jpg "BiometricsRegistration") #### Unrecognized Checkout {#unrecognized-checkout} The following diagram shows the use of fingerprint recognition during the un-recognized checkout flow. ![alt text](https://static.developer.mastercard.com/content/masterpass-merchant-integration-v7/documentation/images/signin-noenrollment-nopreference.jpg "Unrecognized Biometrics Checkout") #### Recognized Checkout {#recognized-checkout-1} The following diagram shows the use of fingerprint recognition during the recognized checkout flow. ![alt text](https://static.developer.mastercard.com/content/masterpass-merchant-integration-v7/documentation/images/recognized-yesenrollment-fppreference.jpg "Recognized Biometrics") #### PIN Support {#pin-support} * Mastercard has enabled PIN entry for consumers in India. Consumers are now prompted to create a 4 digit PIN as well as a password when creating their Masterpass account on an iOS or Android device. They will then need to re-enter the PIN as a method of authentication when making subsequent purchases using the recognized checkout flow. If a consumer forgets their PIN, they will need to use their password instead and will be prompted to create a new PIN to use in future. Note: The PIN cannot contain repeated or consecutive numbers. ![alt text](https://static.developer.mastercard.com/content/masterpass-merchant-integration-v7/documentation/images/01-registration-w-pin.jpg) ![alt text](https://static.developer.mastercard.com/content/masterpass-merchant-integration-v7/documentation/images/01-recognized-w-pin.jpg) ### 3D Secure {#3d-secure} The Merchant embedded native experience provides further authentication by implementing an embedded 3D Secure 1.0. screen. #### Pre-Conditions {#pre-conditions-3} * The Merchant application is Masterpass enabled. * The Merchant has enabled 3D Secure. Masterpass prompts consumers to complete second factor authentication by entering their secure PIN. 3D Secure may be triggered in the following user flows: * Checkout with card during recognized checkout. * Checkout with card during unrecognized checkout. The following image shows an example 3DS screen within the Merchant embedded native experience: ![alt text](https://static.developer.mastercard.com/content/masterpass-merchant-integration-v7/documentation/images/3ds-screen.png "3DS Mobile") #### Additional Factor Authentication (AFA) Relaxation - Available in India only {#additional-factor-authentication-afa-relaxation---available-in-india-only} The 3D Secure check can be surpressed (relaxed) for Indian merchants for amounts under 2000 Rupees. Relaxation takes place if all the following conditions are met: * The merchant is based in India * The selected payment card is part of a BIN range which an Issuer has enabled for AFA Relaxation. * The transaction amount is \< = 2000 Rupees If AFA relaxation occurs, Masterpass will return an ECI value of 05 and a Masterpass generated AAV value in the cAVV field.