Help

Contact support effectively

A concise reproducible report saves follow-up questions.

1 min read · 123 words

A concise reproducible report saves follow-up questions. 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 concise reproducible report saves follow-up questions. This guide covers 3 practical actions, in the order they usually happen.

Do this first

State what you were trying to do..

Give the page, time, and exact visible error..

Then finish with

Include a redacted screenshot only if it helps explain the problem..

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.