Help
A comment did not appear
A slow or failed request should be checked before resending.
1 min read · 126 words
A slow or failed request should be checked before resending. 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.
A slow or failed request should be checked before resending. This guide covers 3 practical actions, in the order they usually happen.
Do this first
Keep a copy of your comment text..
Reopen the comments and look for the saved reply..
Then finish with
Retry if it is absent and the error is resolved..
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.
Need help with a specific error? Contact Merchant Bridge with the page and visible error, without passwords or secret keys.