# SDK MercadoPago.js V2
## Table of Contents 1. [About](#about) 2. [Support](#support) 1. [Desktop web](#desktop-web) 2. [Mobile web](#mobile-web) 3. [Installation](#installation) 4. [Initializing](#initializing) 5. [Checkout API](#checkout-api) 6. [Checkout Pro](#checkout-pro) 7. [API](#api) 8. [Notes](#notes)
## About It is a **clientside SDK** whose main objective is to **facilitate the integration of Mercado Pago payment solutions on your website**, thus allowing a secure flow and within the security standards of sensitive data transfer.
## Support ### Desktop web | Browser | Support | | ----------------- | -------- | | Chrome | 80+ | | Firefox | 74+ | | Safari | 14+ | | Edge | 80+ | | Opera | Complete | | Internet Explorer | 11 |
### Mobile web | Browser | Support | | --------------- | -------- | | Chrome | 80+ | | Firefox | 74+ | | Safari | 13.3+ | | Android Browser | Complete |
## Installation To install the SDK, you must include the script in your application's HTML or install a package on `npm` ```html ``` or ```javascript npm install @mercadopago/sdk-js; ```
## Initializing To start the SDK, you need to assign your `public_key` along with some `options`. If you are using `html` reference: ### Example: ```javascript const mp = new MercadoPago("YOUR_PUBLIC_KEY", { locale: "en-US", }); ``` If you are using `npm` package: ### Example: ```javascript import { loadMercadoPago } from "@mercadopago/sdk-js"; await loadMercadoPago(); const mp = new window.MercadoPago("YOUR_PUBLIC_KEY", { locale: "en-US", }); ```
## Checkout API Use our APIs to build your own payment experience on your website or mobile application. From basic to advanced settings, control the entire experience. There are multiple supported ways to integrate Checkout API. Ranging from the most simple integration, using Checkout Bricks, to integrating with the Core Methods, where the integrator has total control of the checkout experience. For a complete reference on the integration options, check the [API reference](#api)
Full example using Bricks ```HTML
```
Full example using cardForm ```HTML
Carregando...
```

## Checkout Pro Checkout Pro is the integration that allows you to charge through our web form from any device in a simple, fast and secure way. See the [API reference](#api)
Full example using Checkout Pro ```html
```

## API ### MercadoPago(`public_key`[`, options`]) SDK instantiation method. #### Params: `public_key` | _string_, **REQUIRED** It is the public key for your account.
`options` | *object*, **OPTIONAL** | Option name | Values | Default | Type | Description | | | ------------------------- | ----------------------------------------------------------------------------------------------- | ---------------------- | --------- | ------------------------------------------------ | ------------ | | `locale` | `es-AR`
`es-CL`
`es-CO`
`es-MX`
`es-VE`
`es-UY`
`es-PE`
`pt-BR`
`en-US` | Browser default locale | _string_ | Set the locale | **OPTIONAL** | | `advancedFraudPrevention` | `true\|false` | true | _boolean_ | Set the advanced fraud prevention status | **OPTIONAL** | | `trackingDisabled` | `true\|false` | false | _boolean_ | Enable/disable tracking of generic usage metrics | **OPTIONAL** |
#### Example: ```javascript const mp = new MercadoPago("PUBLIC_KEY", { locale: "en-US", advancedFraudPrevention: true, }); ```
#### Return: `mp instance` Check the reference for all SDK modules. | | | --------------------------------------- | | [Checkout Bricks](/API/bricks/index.md) | | [Card Form](/API/card-form.md) | | [Core Methods](/API/core-methods.md) | | [Secure Fields](/API/fields.md) | | [Checkout Pro](/API/checkout-pro.md) |
---
## React library The [React SDK library](https://github.com/mercadopago/sdk-react) makes the integration even easier. It is a wrapper that allows integrate Checkout Bricks easily inside React projects. > Currently available for Checkout Pro and Checkout Bricks ```js import { initMercadoPago } from "@mercadopago/sdk-react"; initMercadoPago("YOUR_PUBLIC_KEY"); ``` ## Notes When requesting our SDK (https://sdk.mercadopago.com/js/v2), we may ship different script based on the browser's User Agent so we can optmize the bundle size according to the needs. For IE 11 we ship polyfills so you can get a better experience when integrating with our SDK