FAQ

This page describes common issues encountered during the consent flow.

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, or your browser may display a “Page unavailable” or “Page isn’t working” message.

Possible causes include:

• One or more Open Authorization (OAuth) parameters are missing, invalid, or incorrectly formatted.
• In the User Acceptance Testing (UAT) environment, the Internet Protocol (IP) address used for the request may not be allowlisted.
• A supporting service or internal component may be unavailable.

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

1. Open your browser’s Developer Tools before you log in.
2. Select the Network tab.
3. Reproduce the issue and look for failed or timed-out requests, such as ERR_TIMED_OUT.
4. Export the network activity as a Hypertext Transfer Protocol Archive (HAR) file.
5. Note the Internet Protocol (IP) address used to make the request.
6. Send the HAR file and IP address to the support team for investigation.

Why won’t the consent page load after I log in successfully?
You may see a 404 or 500 error if a supporting service is unavailable or a network request fails.

To troubleshoot:

1. Open your browser’s Developer Tools.
2. Select the Network tab.
3. Reproduce the issue and look for failed requests.
4. Export the network activity as a Hypertext Transfer Protocol Archive (HAR) file.
5. Send the HAR file to the support team for investigation.

Support and help

Where can I find the steps to onboard and integrate with the 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.