> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment Verification with the Connect Widget

<Note>
  **LEGACY GUIDE**

  This guide is for Platform API v2011101. For guidance on the newest version, see [Connectivity Integration Guides](/products/connectivity/overview/connectivity-integration-guides/).
</Note>

This guide uses our Connect Widget to gather end user’s credentials and fetch the appropriate data to enable payments.

To learn more about the widget, see [Connect Widget](/connect).

We’ll use our Widget SDK to integrate the widget into your application. For more information on the Widget SDKs, see [Implementation Guides](/connect/guides/). Your integration method depends on whether you’re building a web or mobile application. If you’re building a web application, use our Web Widget SDK. If you’re building a React Native application, use our React Native Widget SDK.

To make this guide easier to follow, we don’t cover [multifactor authentication (MFA)](/products/connectivity/overview/mfa) or [OAuth](/resources/oauth-guide). We have in-depth guides on how to manage MFA or OAuth depending on the product you’re using.

<Info>
  **INFO**

  The Platform API is required for this use case. If you are a legacy client using the Nexus or Atrium API, the following information may not apply.
</Info>

## Before you Begin

Before you can you can use this guide, complete the following:

* Sign up for the [Client Dashboard](https://dashboard.mx.com).
* Retrieve your `client_id` and `api_key` from the dashboard; you’ll need them to pass requests.
* Whitelist your IP addresses.
* Ensure all requests are using HTTPS with TLSv1.2 encryption or higher or else they will fail.
* Get familiar with [MX Bank, our test environment](/resources/test-platform); MX Bank only allows specific test scenarios; and our guides follow these test experiences.
* Work with your MX representative to enable the products required for your use case, which may include the following:
  * Instant Account Verification (IAV)
  * Account Owner Identification
  * Balance Checks