99 clubOpen account access
Home / Payments

Payments

Review the details of a payment query, distinguish pending and completed entries and prepare a record with sensitive fields removed.

Clipped transaction receipts

Build a private record of the event

Start with the service where you initiated the transaction. Write down its displayed time, amount, status and reference in your private notes. Then look at the entry in your banking or payment application for the same time. Compare the identifiers where available. A matching amount can occur twice in one day, so amount alone is a poor way to link two records.

Understand what each screen can tell you

A bank notification records something the bank observed. A destination account screen describes the status held by that service. One can change before the other. Keep the exact words shown on each screen instead of replacing both with a single conclusion. A pending entry, for example, does not by itself tell you whether a fresh payment is necessary or appropriate.

Decide who can answer the question

If the issue concerns a bank-side entry, open your own bank application and find its contact route there. If it concerns how an account service recorded a payment, use that service’s account support process. Give the responsible provider only the information its enquiry procedure requires. A public site query about a broken link does not require sharing your financial record.

Prepare the smallest useful attachment

Inspect the entire image before sending it. A screenshot of one entry can include a balance, account identifier, unrelated payments or a notification at the top. Crop those areas or describe the status in words instead. Keep any full reference needed by the provider in a private channel. Never send a PIN, password or one-time authorisation code to someone offering to investigate a payment.

For your own notes, keep the original status wording in quotation marks so that a later update is easy to recognise.