In this guide
Approval Plus Mortgage
Practical guides

Prepare a payment screenshot that is useful and safe to send

A good screenshot answers one support question without exposing the rest of your account. Prepare a minimal image, check the saved copy and send it through the correct channel.

Choose the question before capturing the screen

Write one sentence explaining what you want investigated: a funding request still awaiting review, a merchant order with an unclear result, or an account-page error. Identify which record belongs to that question. An Approval Plus funding request, a blockchain transfer and a merchant invoice are separate records; a screenshot of one should not be labelled as proof that another has completed.

Choose the smallest view that retains the relevant status, amount with currency, date, reference and error text. If a merchant invoice is the issue, include its invoice or order reference rather than a full card-details page. For a transfer issue, preserve the network and asset names. Close unrelated tabs, account menus and notification popups before capturing anything.

Sources & further reading: [1]

Decide what must stay and what must be removed

Keep the label beside each useful value so support can tell an order number from a funding request reference. A masked card reference may help distinguish two records, but a full card number, CVV, account seed, wallet recovery phrase, private key or authentication code does not belong in a support image. Remove unrelated email addresses, conversations and account balances as well.

For an invented example, a useful image could show Request EXAMPLE-42, USD 100, USDC, the selected network and the observed status. The accompanying message can state when the transfer was submitted. The example is not a real request or receiving address. Do not replace an actual error message with your interpretation; keep the wording visible and explain your interpretation separately.

Sources & further reading: [1]

Create a separate shareable image and inspect every hidden area

Crop out unnecessary material first. Where a sensitive value remains inside the required area, use a proper redaction function or remove the pixels with an opaque cover in a separate image copy. A translucent highlighter or a loose pen stroke can leave characters readable. Avoid sending an editable document that retains the original picture beneath a removable annotation.

Microsoft’s Snipping Tool documents Quick redact for email addresses and phone numbers. That is not a complete checklist for payment secrets. Inspect the image yourself for seeds, card credentials, QR codes and information inside notifications. If the tool cannot hide a value confidently, take a new capture that excludes it or describe the non-secret error in text instead.

Sources & further reading: [2]

Verify the exact file that will be attached

Save the shareable result as a new image with a neutral name, then open that saved file outside the editor. Zoom in on the covered areas and check the image edges. Confirm that the original seed, full card number or secret QR code is absent, while the status and relevant reference remain readable. An editing preview is not the attachment you are about to send.

Use an obvious filename such as funding-status-redacted.png and keep it distinct from the original. In the email draft, open the actual attachment once more; do not rely on a similar thumbnail or a filename ending in a number. This final check catches the practical mistake of editing one image and attaching the unedited capture. Remove unnecessary originals from shared locations after preserving any legitimate private records.

Send a concise explanation through the real support route

The dashboard’s Support area lets you choose New conversation, enter a category, subject and message, and select Send message. A successfully submitted conversation opens inside your account, where Send reply adds a further message. That form accepts text rather than screenshot attachments. To send an image, use the support email shown on the genuine contact page, review the recipient and checked attachment in your email application, and send it deliberately.

Include the request or order reference, amount and currency, network when relevant, observation time and the exact question. A complete transfer hash can be supplied privately where needed; it connects public blockchain information and should not be posted casually. Never attach your account seed to prove ownership. Keep the sent message and reply together so later updates refer to the same question.

Sources & further reading: [1] [3]

Your questions, answered

Can I use a coloured highlighter to hide my seed?

Do not send a seed screenshot. For other sensitive fields, use proper removal or opaque redaction and inspect the saved image. If there is doubt, capture a smaller view or send only non-secret text.

Does Send message upload my screenshot?

No. The in-account support form submits text. To provide a screenshot, use the support email from the genuine contact page, attach only the checked image, review the recipient and send it from your email application.

Should every detail in a screenshot be hidden?

Keep the information needed to understand the issue: the relevant reference, status, amount, currency and time. Remove secrets and unrelated personal information without changing the meaning of the record.

Sources & further reading

  1. Approval Plus: account, funding and support help ↗Checked Nov 16, 2026
  2. Microsoft: screenshot capture and text redaction in Snipping Tool ↗Checked Nov 16, 2026
  3. Approval Plus: support contacts ↗Checked Nov 16, 2026
APPROVAL PLUS

Your next step

Account, funding and card guidance in your language.

APPROVAL PLUS

Need a hand?

Our support team can help with your account, funding and card questions.

support@approvalplusmortgage.com