Help

A message failed

Keep private message content out of public troubleshooting posts.

1 min read · 118 words

Keep private message content out of public troubleshooting posts. Support can investigate a specific page, account-access problem, or failed action. Include the route, time, and visible error. Do not send passwords, API keys, access tokens, or entire recipient lists.

What to expect

Support can investigate a specific page, account-access problem, or failed action. Include the route, time, and visible error. Do not send passwords, API keys, access tokens, or entire recipient lists.

Keep private message content out of public troubleshooting posts. This guide covers 3 practical actions, in the order they usually happen.

Do this first

Check your session and connection..

Reopen the intended conversation..

Then finish with

Contact support with the error and conversation reference if necessary..

Good to know

Everything here reflects the current Merchant Bridge interface. Labels and buttons may move as the product evolves, but the flow stays the same: prepare, act on the page this guide references, and confirm the result before moving on.

When something does not match what you see, the destination page for this guide is the source of truth.

Open support

Need help with a specific error? Contact Merchant Bridge with the page and visible error, without passwords or secret keys.