Each guide should solve a distinct problem
We write for people trying to understand a reference, document, status or next step. An explanation of a payment instruction serves a different purpose from a bank-trace checklist. We link related material rather than repeating the same article under different headings.
Educational content does not represent a bank investigation or personalised financial or legal advice. A guide must distinguish an instruction, a reported stage and a confirmed account entry when that distinction affects the reader’s decision.
Prefer the source responsible for the claim
For message terminology and network processes, we prefer standards bodies and Swift documentation. For a bank’s fee or procedure, we prefer that bank’s own material. For fraud reporting and consumer protection, we use the relevant public authority and identify geographic limits.
We link sources near the explanation they support. A provider-specific example is not presented as a universal banking rule. Third-party references do not imply endorsement of UETR.io.
Examples need boundaries
Illustrative references, amounts and routes help explain a concept. They do not identify a live transfer unless explicitly described and appropriately sourced. A demonstration must not be presented as proof of payment, a guaranteed arrival estimate or a promise of recovery.
Descriptions of this service should match its implemented behaviour. UETR.io displays registered records; the guides must not imply that the public lookup independently queries the live SWIFT gpi network.
What publication and source-check dates mean
A publication date identifies when a page was first published. A source-check date records when the linked evidence for that guide was checked; it does not mean every bank has adopted the same procedure or that a provider cannot change its terms afterwards.
We aim to revisit material when a referenced rule changes or a specific concern is raised. We do not claim a fixed review schedule or review by a named professional where neither has been established. Significant factual changes should be made clear in the affected guide.
Send a correction we can investigate
Email [email protected] with the page URL, the exact statement, why it may be wrong and a primary source if available. You can also report a broken link or a tool result that conflicts with its stated rules.
Please exclude personal account details, payment documents and signed transaction links. We assess the claim against the relevant source and the service’s actual behaviour. A correction request does not require us to endorse an unsupported claim or publish private information.
For a security issue, use the reporting guidance on Security & Data Access. For a bank dispute, use your bank’s complaint procedure rather than an editorial enquiry.