A recurring package sold to “providers” and “receivers” describes institutional transfers via invented FTP procedures and FIN 103+ style steps. The language borrows SWIFT-adjacent vocabulary so the process feels real.
Independent banking practice does not run on mystery FTP scripts emailed as Word/PDF “procedures.” When a desk cannot explain a step in terms a regulated bank officer would recognise, treat the pack as theatre.
Red flags in “procedure” packs Unverifiable timelines; non-standard message codes; fees before any bank-to-bank confirmation; refusal to let your own bank verify the path.
What to verify instead
- Call your bank’s known number — not a number from the PDF
- Ask whether the described message type is used for that product
- Refuse sequential “procedure fees” before independent confirmation
If the procedure only exists inside the scammer’s document, it is not a bank procedure.
Standards: Scam Wire publishes document patterns and public red flags. We do not invent convictions. Names appear as they surface in tips and document trails. Independent verification always comes first.
Tips: tip desk · Archive: case files.