OPERATIONS — 9 MIN READ
MT103 Stuck Payment Operations Runbook
Follow an MT103 stuck-payment runbook: detect, classify, escalate, and evidence resolution without unsafe duplicate re-initiation across correspondent rails.
|
Stuck is a state machine, not a vibe
An MT103 is stuck when expected status or credit confirmation does not arrive within corridor SLAs. The runbook must detect, classify (network, compliance, beneficiary, intermediary), escalate, and close with evidence—without sending a second payment.
globalserverbank is not a licensed bank or SWIFT operator and is not affiliated with Visa.
Align investigation statuses with Global Server Protocol and MT103 coverage.
Detect, classify, act
Detect via aged pending queues keyed by UETR/end-to-end ID. Classify using last known agent status and pacs.002 where available. Act with investigation messages, returns/recalls per MT103 return procedures, or controlled repair—never blind resend with a new reference.
Preserve the audit trail for regulators and counterparties.
Tooling and hosting
Case tools and gateways belong on controlled cloud banking servers with dual control for any resubmission path.
CTAs
cross-border settlement, node access, Global Server Protocol.
FURTHER CLARITY
Frequently asked questions
When is resubmission allowed?
Only under explicit policy after confirming the original never settled and counterparties agree—still prefer return/repair paths.
What SLA starts the stuck clock?
Corridor-specific; document it per currency and intermediary chain.
Can globalserverbank unstick a live wire?
No. It does not operate rails or hold 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.