Skip to main content
J.P. Morgan Business Direct Connect

FAQs

This page describes common issues encountered during the consent flow.

Note

Before logging in: Open your browser’s Inspect page or Developer Tools. This allows you to monitor request statuses in the Network tab and makes debugging easier if issues arise.

What can I do if the login page won’t load from the authorization URL?
You may see a 400, 403, 404, or 500 error, page unavailable, or page isn’t working.

  • Check your OAuth parameter values against the integration guide. Make sure each value is correct and in the right format.
  • If you’re seeing this in the UAT/test environment, your IP addresses may not be allowlisted.
  • An internal component is failing.

To troubleshoot, open your browser’s Developer Tools before you log in, then:

  1. Go to the Network tab.
  2. Look for errors like ERR_TIMED_OUT.
  3. Export the HAR file.
  4. Note the IP address that you’re making the request from.
  5. Send the HAR file and the IP address to our support team so we can investigate.

Why won’t the consent page load after I log in successfully?
You may see a 404 or 500 error. This can happen when a subsystem is down or a network call fails.

To troubleshoot, open your browser’s Developer Tools and:

  1. Go to the Network tab.
  2. Look for failed requests.
  3. Export the HAR file.
  4. Send the HAR file to our support team so we can investigate.

Support and help

Where can I find the steps to onboard and integrate with Business Direct Connect API? 

Use the integration guide for step-by-step instructions.

How can I get more help with integration and production issues?

Use the support page for contact details regarding integration testing and production support.