Using screenshots as useful evidence in a Fair Go dispute
You have taken a screenshot because something did not look right on your Fair Go account, and now you are checking whether it actually supports the point you want to make. A picture of a screen can be valuable, but it only records what was visible at that moment. Deciding what to keep and what to hide is easier once you separate the evidence you need from the private information around it.
What a Fair Go screenshot can and cannot establish
A screenshot captures the state of a page at one moment, so treat it as a record of what was displayed rather than a complete account of what happened. If your concern is a balance, the image shows the figure that appeared when you took it, but it cannot explain why that figure changed or whether a payment had completed behind the scenes. A single balance image cannot supply an earlier balance, so it will not prove a movement on its own. Keep the before and after times explicit in your written explanation, and acknowledge any other activity on the account that could account for the difference. That honesty makes the screenshot more credible, not less, because it shows you are describing the sequence rather than asking the image to carry a conclusion it cannot support.
A confirmation screen deserves the same restraint. A request or payment-service confirmation is not by itself proof that the receiving account was credited, and a Fair Go page showing a submitted request does not establish that funds arrived elsewhere. If you need to demonstrate a payment outcome, the strongest evidence is usually a record from the payment side showing the movement, paired with your account history. Where you do not have that record, describe the gap directly: say what the screenshot shows, what it does not show, and what you are asking to be checked. That framing keeps the dispute focused on a verifiable question rather than on an assumption drawn from a single screen. Before making a decision involving https://unitedrepublic.org/, retain useful evidence while removing unrelated private details from the shared copy.
Worked example of a balance difference where the image falls short
Suppose you check your Fair Go balance at 9:10 in the morning and note a figure, then look again at 11:40 and see a lower amount. You screenshot the 11:40 page because that is when you noticed the problem, but the image alone cannot show the 9:10 figure or what happened between the two times. A proportionate next step is to write down both times and both amounts, note any activity you know about in that window, and look for an account history view that lists transactions with timestamps. If such a history is available, a screenshot of it alongside your note gives the earlier figure a source. If no history is visible, say so, and explain that you are relying on your own record of the earlier balance.
Now imagine you send that 11:40 screenshot with unrelated details visible: your full name, an email address, a partial card number, and the name of another person in a message panel. Cropping those areas or covering them with opaque, flattened redaction protects information that has nothing to do with the balance question. Avoid thin scribbles or translucent highlights, because text underneath can sometimes still be read. After you prepare the file, reopen the shared copy and check it at full size to confirm the private details are gone and the balance and timestamp remain legible. Different partial images are not automatically stronger evidence; two unclear crops can be weaker than one clean image with a written timeline beside it.
Deciding what to keep, hide and send to Fair Go
Start by naming the single point you want the screenshot to support, such as the amount displayed at a particular time or the wording of a confirmation. Then ask whether the image shows that point directly. If it does, keep the part that carries the detail and remove the surrounding private information. If it does not, add a short written explanation of what is missing rather than collecting more partial images. Compare the intended action with what the confirmation actually says, word by word, because a page can confirm that a request was received while saying nothing about completion. That comparison often tells you whether you need a different record entirely, such as a payment-service receipt or an account history entry.
When you send anything to Fair Go support, keep the message proportionate: one or two clear images, a short timeline, and an explicit statement of what you are asking to be reviewed. Do not assume Fair Go provides a particular upload tool, search function or account export unless you have seen it in your own account; describe what you have and ask how best to supply it. Store the original file and a redacted copy separately so you can refer back to the unaltered version if the edited one is questioned. Finally, reopen the exact copy you plan to share and verify it, because the check you do before sending is the step that keeps useful evidence intact while unrelated private information stays out of the conversation.
The screenshot is only as good as the story it supports, so match the image to the exact point you are making, record the timing clearly, and remove anything private that does not help. Check the shared copy before sending it, because a cropped file that still reveals unrelated details is weaker than a careful one. If your current evidence cannot show the earlier balance or the arrival of funds, say so plainly rather than overstating what the picture proves.