MX Integration Overview

MX is a financial data platform that allows businesses to verify bank accounts and confirm account ownership. Persona’s integration with MX brings these verification capabilities directly into your workflows.

This integration eliminates manual verification steps and context switching by automating bank account verification from Persona. It is especially helpful for fraud prevention and regulatory compliance.

Benefits

Automated Bank Verification: Verify account ownership in real time, reducing manual work and errors.

Fraud Mitigation: Detect mismatches between provided account information and verified bank records.

Streamlined Workflows: Access MX verification results directly within Persona workflows.

Integration Features

Persona’s MX integration brings bank account verification directly into your workflows. Key capabilities include:

• Automated Account Verification: Instantly confirm account ownership and reduce manual verification steps.

• Fraud & Compliance Checks: Detect mismatches between user-provided data and verified bank records to mitigate fraud and stay compliant.

• Workflow Integration: Access MX results within Persona workflows to trigger automated actions like approval, decline, or review.

Setting Up the MX Integration

Prerequisites

• Admin access to your Persona org.
• MX API credentials (sandbox or production).

Adding MX Credentials

1. Navigate to Integrations > Marketplace in the Persona Dashboard and click on MX.
2. Click Add API Key.
3. Select whether you have a Sandbox or Production API key.
4. Enter the MX credential information in the modal.
5. Save and confirm the connection.

Using the MX Integration in a Workflow

1. Create a new workflow or open an existing workflow.
2. Add a new action step → Integrations.
3. Select the MX Bank Verification integration and enter your MX credentials.
4. Configure the input fields for the workflow (e.g., first name, last name, account number, routing number).
5. Save and publish the workflow.

MX Operations Overview

List Users

Retrieve a list of MX users to manage bank verification records or perform lookups.

Configuration Steps:

Provide values for required fields:

• API version header

Optionally add:

• Page number
• Records per page
• User ID
• Email address
• Is disabled (indicate whether an MX User record is active or deactivated/disabled)

Create User

Create a new MX user to initiate verification or microdeposit flows.

Configuration Steps:

Provide values for required fields:

• API version header
• Email address
• User ID

Optionally add:

• Is disabled
• Metadata

List Account Owners by Member

Retrieve verified account ownership information associated with a specific member.

Configuration Steps:

Provide values for required fields:

• API version header
• Member GUID (unique ID for a member)
• User GUID (unique ID for a user)

Optionally add:

• Page number
• Records per page

Read a Microdeposit for a User

Review the status of a microdeposit to confirm bank account ownership.

Configuration Steps:

Provide values for required fields:

• API version header
• User GUID
• Microdeposit GUID (unique ID for a microdeposit)

Request Widget URL

Generate a secure, embeddable widget URL to initiate MX Connect or Verification flows.

Configuration Steps:

Provide values for required fields:

• API version header
• User GUID
• Widget Type (e.g., connect_widget)

Optionally add:

• Language
• Client Redirect URL
• Color Scheme
• Current Institution Code / GUID / Member GUID
• Disable Background Aggregation
• Disable Institution Search
• Include Identity
• Include Transactions
• Insight GUID
  • If relevant, select “Is Mobile Webview”
• Microwidget Instance ID
• Mode (e.g., verification)
• OAuth Referral Source
• UI Message Version
• UI Message Webview URL Scheme
  • If relevant, select “Update Credentials”

FAQs

What banks are supported?

Primarily U.S. banks, with limited coverage in Canada.

Do I need OAuth registration for some banks?

Yes, certain banks require the customer to register their OAuth connection. Approval times vary.