For eligible payment instructions carried over Swift, the UETR is a 36-character unique end-to-end reference. Payment institutions create or relay it and can use it to trace status across the Swift payment chain. See Swift’s UETR guidance.

The receipt may instead show a bank transaction reference, Application ID, outward-remittance reference, or another internal identifier. A bank may map that value to a UETR, display both, or expose neither in its customer channel. Do not assume the short value is equivalent to the UETR.

Check the current transfer receipt and detailed transaction view for a 36-character hyphenated value labelled UETR or Unique End-to-End Transaction Reference. Do not alter, shorten, expand, or invent an identifier.

If you need the UETR or a payment trace, contact the sending bank and provide the transaction date, amount, currency, beneficiary, and receipt reference. Ask whether the payment used Swift, request the exact UETR if one exists, and request the current trace or status.

Customer access, available fields, status detail, and response time depend on the bank, payment route, and service. A short reference may work in a bank’s own tool but is not a substitute for the UETR unless the bank or FXTRADING.com confirms that for the specific case.

If FXTRADING.com asks for the UETR, send the exact bank-provided 36-character value and the requested receipt evidence through the current official secure support route. Do not send banking passwords, PINs, OTPs, or unrequested full statements in ordinary chat or email.

FXTRADING.com can investigate only with the records and identifiers received and does not control a bank’s tracker, response, recall, crediting, or timing. If funds were sent using incorrect or unsupported bank details, contact the sending bank promptly to request a trace or recall and notify FXTRADING.com through the official support route; recovery and timing are not guaranteed. Keep all references private except when sharing them through the secure case.