Tracking a Fair Go transaction on a narrow phone screen
You moved from a desktop to a phone, and now the transaction you are trying to match to a reference and a processing stage is harder to read. The same records are probably there, but a narrow screen can hide column headers, push dates onto separate lines and make a reference number wrap so it no longer looks like one piece of information. This article shows how to slow the task down, keep the stages separate and reach a conclusion you can trust rather than one based on a single crowded screen.
Reading a Fair Go transaction reference and stage on a narrow screen
On a wide screen, a table often shows the amount, the reference and the status side by side, so your eye links them automatically. On a phone, those same fields may stack vertically, and the header that tells you what each line means can scroll out of view. Before you decide anything, note the unit label attached to each value. An amount should carry a currency label, such as AUD, while a reference is an identifier and should be treated as text even if it happens to contain only digits. Do not reclassify a large number as an identifier, or a small one as an amount, just because it looks unusual; the label and its context decide what the value is. If two labels seem to conflict, ask Fair Go to clarify rather than guessing which one is right.
The processing stage is a separate question from the reference. A record can show that a request was received without showing that it has been processed, completed or credited on the receiving side. Those are distinct points, and a phone layout may display only one of them at a time. If a stage label is cut off or ambiguous, treat it as unclear. A pending label on its own does not prove that a hold exists, and a missing visible record does not prove that something failed. Read the elements you can see, write them down in the order they appear, and then decide what still needs checking instead of acting on a single screen.
A hypothetical phone reconciliation with an amount, reference and date
Suppose you made a transfer of 250.00 AUD and noted a reference beginning with FG. On your phone, the history view shows three stacked blocks. The first reads 250.00 with an AUD label and a date of 14 March. The second shows a long string that wraps across two lines and includes letters and digits. The third says pending. On a desktop these may have sat in one row under clear headers; on the phone the headers are gone, so you must rebuild the row yourself. Match the currency-labelled amount to the reference you recorded, then check the date in its day-month context. The wrapped string is still one identifier, so compare it in full rather than matching only the first few characters. When you are considering options connected with unitedrepublic.org, match the reference and processing stage to the original action.
Now separate the stages. The received stage is evidenced by the request appearing at all. The processing stage is what the pending label may refer to, but it does not confirm a hold. Completion and receiving-side credit are later points that this screen does not show. The disciplined move is to reconcile the records you have: your own note of the reference and date against what Fair Go displays, and any receiving record against the same identifier. Do not repeat the operation because one screen is incomplete. If the amount label and the reference appear in an order that contradicts your note, or a label is truncated, ask Fair Go to confirm which value is which before you draw a conclusion.
Applying the phone check to your own Fair Go records
Take your own case one field at a time. Rotate the phone or widen the text only if that helps you read full labels, and use whatever record view or search function Fair Go makes available to you, if one exists; do not assume a particular menu or filter is there. Start with the amount and its currency label, then the reference as a complete identifier, then the date with its unit and context. Compare each against your own note of what you sent. Where a value wraps or a header disappears, write the field down in plain text so the narrow layout stops influencing how you read it. This keeps you from mistaking a display problem for a discrepancy.
Then map what you see onto the stages. Note whether the record shows receipt, processing, completion or receiving-side credit, and mark any stage the phone view does not display as unknown rather than failed. If the reference matches and the amount and date agree, the remaining question is the stage, and that is the question to put to Fair Go. If they do not agree, describe the exact conflict, including the labels, and ask for clarification. You are not trying to force one balance difference to explain everything; you are reconciling the relevant records until each field and stage has a clear answer or an acknowledged gap.
The narrow screen did not change your transaction, but it did change how easily you can read the reference and the stage. By treating the currency-labelled amount, the full identifier and the dated record as separate fields, and by keeping receipt, processing, completion and receiving-side credit apart, you can match your Fair Go record to your own note without guessing. If a label remains unclear or a stage is not shown, the honest result is a specific question for Fair Go rather than a repeated operation, and that question is the next step this situation calls for.