Start with the transaction reference
A reference connects a question to a particular operation. It is more precise than an image of an entire account dashboard and easier to use when several transfers have similar amounts. WATADCASH’s transfer guides tell users to retain the request reference for follow-up, while its USDT guide also refers to the sending transaction identifier.
Share the reference through the official support process or with the intended recipient where appropriate. Explain what the reference relates to and which state you can see. A collection of unexplained numbers is less useful than one identified request and a short description of the issue.
Keep access credentials out of the conversation
A password, recovery phrase or private key provides a different kind of information from a transaction reference. It can enable access or control. Those secrets should not be included in a payment enquiry, even if someone claims that doing so will speed up an investigation.
The same principle applies to business integrations. WATADCASH’s developer documentation says integration keys belong on the server. An API key is not a receipt. When requesting technical help, use a placeholder in example requests and describe the relevant permission or error without publishing the credential’s value.
Review screenshots before sending them
Screenshots can show a status or an error message clearly, but they may also reveal unrelated information. Before sharing one, look beyond the part you intended to capture. Remove unnecessary account details, other transactions and sensitive card information. Keep the remaining image connected to the support reference.
Do not confuse a screenshot with authoritative proof that a merchant has received payment. WATADCASH’s gateway guidance tells merchants to verify payment on their server rather than relying on a screenshot, redirect or invoice-creation response. A screenshot can support a conversation while the underlying record supplies the verification.
Use the intended channel and recipient
Send the information to the official channel relevant to the request. A public comment or an unrelated chat is not equivalent to an account support case. If the recipient needs collection instructions, share those instructions and the relevant reference, not the sender’s account login.
For teams, decide who is allowed to see payment records and who can perform actions. A support operator may need to investigate a reference without needing the power to create a withdrawal or issue a card. Clear responsibilities reduce the temptation to share a powerful credential simply because another person needs to answer a narrow question.
Preserve a useful record of the enquiry
Keep the support case reference and the answer that resolves the issue. If the visible transaction state changes, update the same case. This creates a clear history of the question without repeatedly circulating private information.
Account security is not only about strong technical controls. It also depends on ordinary decisions about what information belongs in a conversation. Share evidence that identifies the transaction, keep credentials private and let the provider or merchant verify the underlying state through its authorised process.
Frequently asked questions
Is a transaction reference the same as a password?
No. They serve different purposes. A reference helps identify an operation; a password or secret key can grant access. Share only the information needed for the specific enquiry and use the official channel.
Can a merchant deliver an order based only on my screenshot?
The reviewed WATADCASH gateway guidance says merchants should verify the payment state on their server. A screenshot can help explain a question, but it is not a replacement for that verification.
What should developers put in example API requests?
Use clearly marked placeholders for secrets and keep real credentials on the server. Include the endpoint, relevant permission and a non-sensitive error description when seeking help. Do not paste an active API key into a public issue or article.
Sources and verification
- WATADCASH security policyReviewed 2026-10-18
- WATADCASH authentication documentationReviewed 2026-10-18
- WATADCASH gateway verification guideReviewed 2026-10-18