Integrate with React Native Expo Go - Android - Mercado Pago Developers
Which documentation are you looking for?

Do not know how to start integrating? 

Check the first steps

Integrate with React Native Expo Go

In mobile application development, the need to display web content within the application often arises. For this, there are several options, among which the use of Custom Tabs (for Android) and Safari View Controller (for iOS) stand out. These technologies allow web pages to be opened in a native browser incorporated into the application, providing a smoother and more consistent browsing experience for users.

Before you start integrating Checkout Pro for Mobile, you'll need to have a preference created in your backend. If you haven't already done so, go to Create preference.

In this step we will install and configure the necessary dependencies to implement Custom Tabs in your project developed in React Native.

Use of Expo-Web-Browser


This dependency provides access to the browser, in this case Custom tabs for Android. It also performs redirect handling.

To install it, run the following command in your terminal.


yarn add expo-web-browser

Implementation of Expo-Web-Browser


To implement the Expo-Web-Browser dependency, follow the example below.


import {
} from "expo-status-bar";
import {
} from "react-native";
import {
} from "expo-web-browser";
export default function ExpoWebBrowserExample(url) {
	return ( <
		View style = {
		} > < Button title = "Open Browser"
		onPress = {
			() => openBrowserAsync('YOUR-URL-PREFERENCE')
		/> <StatusBar style="auto" / >
		/View> );
	const styles = StyleSheet.create({
		container: {
			flex: 1,
			backgroundColor: "#fff",
			alignItems: "center",
			justifyContent: "center",

How to return to your app


Deep Links are a powerful way to allow direct navigation to specific screens or sections of a mobile application.

From our checkout, you can configure Deep Links to return to your application, either by clicking a "Back" link or automatically after completing a successful payment flow, redirecting you back to your application.

For this, we must add the back_urls and auto_return properties when creating the payment preference, as needed.

To learn more, you can visit the documentation on Return URLs.


In order to receive and manage the Deep Link, it is necessary to configure in our React Native project the scheme and path that make up the Deep Links that we receive to redirect to some part of your application. To do this, add the following configuration to your app.json file located in the root of your file:


"expo": {
"android": { "intentFilters": [
"action": "VIEW", "data": [
"scheme": "myapp", "host": "checkout", "pathPrefix": "/congrats"
} ],
"category": ["BROWSABLE", "DEFAULT"]
} ]
} }
  • In this example, the deep link expected to redirect to the app is myapp://checkout/congrats
  • The pathPrefix property is optional

In case the project does not have a prebuild yet, you can test the deep link using expo go from the terminal as follows:


// test device local url
npx uri-scheme open exp:// --android
// Note: It is not required to pass the scheme in these tests

In case of running a prebuild of the application, you should verify that the deep link for Android has been configured in the android/app/src/main/AndroidManifest.xml file. The deep link must be between the activity tags.


<activity ....> ....
<intent-filter data-generated="true">
<action android:name="android.intent.action.VIEW"/>
<data android:scheme="myapp" android:host="checkout" android:pathPrefix="/congrats"/> <category android:name="android.intent.category.BROWSABLE"/>
<category android:name="android.intent.category.DEFAULT"/> </intent-filter>


Finally, you will need to configure your React Native application to receive and manage Deep Links. This will be addressed using the react-native-inappbrowser dependency.

In the case of Android, the closing of the custom tab is done automatically when redirecting to a valid Deep Link. In the event that the link is not valid, no redirection action will be executed from the custom tab.