# MD for: https://www.mercadopago.com.uy/developers/pt/docs/checkout-bricks/how-tos/improve-payment-approval/recommendations.md

\# Recommendations to improve payments approval \*\*To prevent a legitimate payment from being refused\*\* because it does not meet the security validations, it is necessary to include all possible information when carrying out the transaction, as well as having your checkout’s interface optimized. You can see our \*\*recommendations to improve your approval\*\* in detail below. ## Get and send the Device ID The \*\*Device ID\*\* is an important piece of information to ensure better security and, consequently, a better payment approval rate. It's a \*\*unique number that's used to identify a customer's device\*\* when they are buying. If a customer makes a purchase on a different device than usual, this may represent an atypical behaviour. Even if it’s not necessarily a fraude, the Device ID could help us to make a correct assessment and avoid legitimate payment rejections. > WARNING > > Attention > > If you are already using the \[JS SDK of Mercado Pago,\](https://www.mercadopago.com.uy/developers/en/docs/sdks-library/client-side/mp-js-v2) it \*\*won’t\*\* be necessary to add the security script because the Device ID information is already being collected. \*\*Add the Mercado Pago security script\*\* to your page by replacing the \`view\` value with the name of the section in which you wish to add it. Adding it to your \*\*checkout URL\*\* is the most important, but doing it in \*\*other pages\*\*, such as home, search or item, may be helpful to collect even more information. \`\`\`html \`\`\` > NOTE > > Important > > In case of unavailable value for a section, leave it empty. ## Implement the Device ID in your site To use the Device ID on your web and prevent possible fraudulent purchases, follow the steps below: ### 1\. Add the security code To generate device IDs on your website, add the following code to your Checkout page: \`\`\`html \`\`\` ### 2\. Getting the device ID When you add the Mercado Pago security code to your site, a global JavaScript variable is automatically created with the name \`MP\_DEVICE\_SESSION\_ID\`, whose value is the device ID. If you prefer that we assign it to another variable, indicate the name by adding the attribute \`output\`, as in the following example: \`\`\`html \`\`\` You can also \*\*create your own variable\*\* by adding an HTML tag on your site as \`id="deviceId"\` and the code will automatically assign the value device\_id. \`\`\`html \`\`\` ### 3\. Use the device ID Once you have the Device ID, you must \*\*send it to our servers\*\* when creating a payment. To do so, simply add the following \*\*header\*\* to the request: \`\`\`http X-meli-session-id: device\_id \`\`\` > WARNING > > Attention > > Remember to replace \`device\_id\` with the name of the variable that contains your Device ID value. ## Implement the Device ID in your native mobile application If you have a native application, you can capture the device information with our SDK and send it when creating the token. Follow these steps: ### 1\. Add dependency 

* [android ](#editor%5F2)
* [ios ](#editor%5F1)
ios android 

Add the following code in the **Podfile** file.

```
use_frameworks!
pod ‘MercadoPagoDevicesSDK’
```

Copiar 

You need to add the repository and the dependency in the **build.gradle** file.

```
repositories {
  maven {
  url "https://artifacts.mercadolibre.com/repository/android-releases"
  }
}
dependencies {
  implementation 'com.mercadolibre.android.device:sdk:4.0.1'
}
```

Copiar 

\### 2\. Initialize module 

* [java ](#editor%5F5)
* [objective-c ](#editor%5F4)
* [swift ](#editor%5F3)
swift objective-c java 

We recommend initializing it in the _didFinishLaunchingWithOptions_ event of the _AppDelegate_.

```
import MercadoPagoDevicesSDK
...
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
  ... 
  MercadoPagoDevicesSDK.shared.execute()
  ...
}
```

Copiar 

We recommend initializing it in the _didFinishLaunchingWithOptions_ event of the _AppDelegate_.

```
@import ‘MercadoPagoDevicesSDK’;
...
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
  ...
  [[MercadoPagoDevicesSDK shared] execute];
  ...
}
```

Copiar 

We recommend initializing it in the _MainApplication_ class.

```
import com.mercadolibre.android.device.sdk.DeviceSDK;
DeviceSDK.getInstance().execute(this);
```

Copiar 

\### 3\. Capture information Execute one of these functions to obtain the information in the format that you prefer. 

* [java ](#editor%5F8)
* [objective-c ](#editor%5F7)
* [swift ](#editor%5F6)
swift objective-c java 

```
MercadoPagoDevicesSDK.shared.getInfo() // Returns a Codable Device Object
MercadoPagoDevicesSDK.shared.getInfoAsJson() // Returns a JSON Library Data Object
MercadoPagoDevicesSDK.shared.getInfoAsJsonString() // Returns a JSON String
MercadoPagoDevicesSDK.shared.getInfoAsDictionary() // Returns a Dictionary<String,Any>
```

Copiar 

```
[[[MercadoPagoDevicesSDK] shared] getInfoAsJson] // Returns a JSON Library Data Object
[[[MercadoPagoDevicesSDK] shared] getInfoAsJsonString] // Returns a JSON String
[[[MercadoPagoDevicesSDK] shared] getInfoAsDictionary] // Returns a Dictionary<String,Any>
```

Copiar 

```
Device device = DeviceSDK.getInstance().getInfo() // Returns a Serializable Device Object
Map deviceMap = DeviceSDK.getInstance().getInfoAsMap() // Returns a Map<String, Object>
String jsonString = DeviceSDK.getInstance().getInfoAsJsonString() // Returns a JSON String
```

Copiar 

\### 4\. Send information Finally, send the information in the \`device\` field when creating the \`card\_token\`. \`\`\` { ..., "device":{ "fingerprint":{ "os":"iOS", "system\_version":"8.3", "ram":18446744071562067968, "disk\_space":498876809216, "model":"MacBookPro9,2", "free\_disk\_space":328918237184, "vendor\_ids":\[ { "name":"vendor\_id", "value":"C2508642-79CF-44E4-A205-284A4F4DE04C" }, { "name":"uuid", "value":"AB28738B-8DC2-4EC2-B514-3ACF330482B6" } \], "vendor\_specific\_attributes":{ "feature\_flash":false, "can\_make\_phone\_calls":false, "can\_send\_sms":false, "video\_camera\_available":true, "cpu\_count":4, "simulator":true, "device\_languaje":"en", "device\_idiom":"Phone", "platform":"x86\_64", "device\_name":"iPhone Simulator", "device\_family":4, "retina\_display\_capable":true, "feature\_camera":false, "device\_model":"iPhone Simulator", "feature\_front\_camera":false }, "resolution":"375x667" } } \`\`\` ## Detail all information about the payment To optimize payment security validation and improve approvals, it is important to \*\*submit as much buyer and item data as possible\*\*. You can check all the available attributes when creating a payment by using the \[Create payment\](https://www.mercadopago.com.uy/developers/en/reference/online-payments/checkout-api-payments/create-payment/post) method. Pay special attention to the attributes present in \`adicional\_inf\`, such as: \* Buyer’s data, \* Product data, \* Shipping data. There are also some \*\*extra fields\*\* that can be sent depending on the \*\*branch of activities or industry of your store\*\*. You can find details of every branch and the buyer and shipping data that we recommend to include for each of them in the documentation \[Additional industry data\](https://www.mercadopago.com.uy/developers/en/docs/checkout-api-legacy/additional-content/industry-data/intro). ## Improve the User Experience Often, the buyer can make mistakes when filling in their details at checkout. That's why it's worth reviewing every step, interaction, and even the interface design, to ensure everything is as clear as it should be. In case you wish to \*\*create your front-end from scratch\*\*, you can find some advice on how to do so in an efficient way \[here\](https://www.mercadopago.com.uy/developers/en/docs/checkout-api-payments/best-practices/ux-best-practices/ux-for-checkouts/introduction). If a payment is rejected, it is also important to explain to your customers why and what they can do to fix it. By doing so, your clients would have all the information they need to pay without any further problems. You can find some \*\*recommendations on how to inform the main rejection reasons\*\* \[here\](https://www.mercadopago.com.uy/developers/en/docs/checkout-api-payments/response-handling/collection-results). In case you wish to guarantee an optimized interface, you can use the \*\*visual components\*\* of \[Checkout Bricks\](https://www.mercadopago.com.uy/developers/en/docs/checkout-bricks/landing), and also use a predefined visual component with the best messages with \[Status Screen Brick\](https://www.mercadopago.com.uy/developers/en/docs/checkout-bricks/status-screen-brick/introduction). > WARNING > > Important > > We recommend checking the results of the \[integration quality measurement\](https://www.mercadopago.com.uy/developers/en/docs/integration-quality) before going to production, whether it has been conducted manually or automatically. This will allow you to validate if you are meeting Mercado Pago's quality and security standards and will provide insights to improve your payment approval rate.