MESSAGING — 9 MIN READ
MT103 Return and Recall Procedures
Run MT103 return and recall procedures with clear status codes, evidence packs, and correspondent coordination—without inventing unauthorized cancellations.
|
Return and recall are different tools
An MT103 return typically moves funds back under defined reason codes after the payment cannot be applied. A recall is a request that counterparties may accept or refuse; it is not a unilateral cancel button on settled cash.
Operators need playbooks that preserve UETR / end-to-end ID continuity and immutable evidence. globalserverbank is not a licensed bank, not a SWIFT operator, and is not affiliated with Visa.
Where ISO 20022 is in use, map procedures to return/status flows and keep Protocol status aligned with Global Server Protocol.
Operational playbook essentials
Classify: undeliverable return, bank-initiated return, customer recall request, compliance freeze. For each, define required evidence, approval matrix, and customer communication rules.
Never re-initiate a new MT103 with a new reference hoping to reverse the old one without correspondent agreement. See MT103 stuck payment runbook and MT103 coverage and status codes.
Log every correspondent response in the audit trail.
Systems and hosting
Case-management and message gateways should share reference data. Host gateways on hardened cloud banking server nodes with dual control for recall initiation.
Legal and product boundaries
Finality rules and scheme manuals govern what can be returned. Architecture help: cross-border settlement, node access, Global Server Protocol.
FURTHER CLARITY
Frequently asked questions
Can I cancel a settled MT103 unilaterally?
Generally no. After settlement finality, you need return/recall mechanisms and counterparty cooperation.
Should recalls track the original UETR?
Yes—follow corridor rules so investigations retain end-to-end continuity even when message types differ.
Is globalserverbank able to recall wires?
No. It does not operate payment rails or hold customer funds.
PRIMARY SOURCES & STANDARDS
References and citations
AN INFORMED NEXT STEP
Bring architectural discipline to your payment and ledger systems.
Start with your architecture, integration boundaries and operational requirements.