Unified Product Ordering

Instead of requesting data from multiple products (such as Instant Account Verification and Account Owner Identification), you can define all desired products in one request. This streamlines the user experience by reducing the number of times users must authenticate with their financial institution, decreases implementation complexity, and ensures consistent data aggregation across your application.

​

Connect Widget Workflow

To aggregate multiple products in the Connect Widget:

1. Call the Request Widget URL endpoint and define the products you want to aggregate. This only starts the aggregation process, so in the next steps you’ll retrieve that aggregated data.
2. Display this widget to the end user.
3. Wait for the end user to connect to an institution and create a member.
4. Verify aggregation is complete by polling the Read Member Status endpoint until member_status.status is CONNECTED and products.last_updated_at is later than when you started the request. See Member Connection Statuses.
5. Fetch the aggregated data using one of the following endpoints:

• List Account Numbers by Member or List Account Numbers by Account
• List Account Owners by Member
• List Accounts or List Transaction by Account
• List Transactions by Member or use another GET Transactions endpoint
• Read Statement by Member or List Statements by Member
• List Holdings by Member or use another GET Investment Holdings endpoint

​

Accessing Priority Data

When requesting products, you can optionally retrieve priority data before all requested data has aggregated. This helps:

• Reduce user drop-off during the connection flow
• Power time-sensitive workflows such as account verification or balance display

Priority data always includes a list of accounts with core details (name, type, and balance if available). Depending on what products you set, it may include account numbers and account owners. You’ll know when priority data is ready via the Initial Data Ready webhook (reach out to MX to enable). You can then close the widget and use the identifiers sent in the webhook to retrieve the priority data, while non-priority data continues to aggregate. The following table outlines what data is available initially and what data is available for you to retrieve later by polling the Read Member Status endpoint until member_status.status is CONNECTED and products.last_updated_at is later than when you started the request.

​

Impact on Conversion

Specifying multiple products within the data_request.products array restricts the selection to institutions that support all the specified services. This selective visibility ensures that users interact only with institutions capable of fulfilling their complete service requirements, enhancing the efficiency and success rate of connections. Further benefits are:

• Streamlined Consent Process: By requesting all necessary permissions during a single OAuth flow, the consent process becomes more straightforward for users. This approach reduces the likelihood of user drop-off caused by complicated consent adjustments.
• Optimized Data Retrieval: Initializing all required products during the connection setup allows MX to commence data fetching immediately. This approach shortens the wait time for data availability and organizes the data retrieval process more efficiently, prioritizing the fetch sequence according to the integration needs.

​

Example Scenario

Suppose you configure the Connect Widget or API to require both Instant Account Verification (account_verification) and Account Owner Identification (identity_verification):

• Institution Availability: Only institutions that support both verification services will be displayed to the user. This filter prevents scenarios where a user attempts to connect with an institution that cannot provide the necessary services.
• OAuth Permissions: If the institution uses OAuth and supports configuring Account Owner data access as a separate permission, users must grant explicit consent for both services. Failure to do so triggers an error, prompting the user to revisit the OAuth flow and adjust their permissions. This ensures that all necessary data accesses are authorized from the outset.

​

Identifying Product Availability

To ensure the data is available for your desired institution, use the products[] query parameter in the List Institutions endpoint, or check the products field in the List Institutions and Read Institution responses.