Quick Fix Summary: Use MT199 for preliminary free-format communication between banks to confirm readiness or share transaction details. Use MT799 solely to verify proof of funds—never as a payment instrument. Both require authenticated channels (MT799 uses test keys; MT199 does not).
What Are MT199 and MT799?
MT199 acts like a secure chat between banks. It handles free-format messages for readiness signals, transaction confirmations, or preliminary details. No funds move with MT199—it’s purely for information exchange. MT799, on the other hand, confirms available funds on deposit at the sending bank. It’s authenticated (using test keys exchanged between banks) but still isn’t a payment or commitment to pay.
These messages run on the SWIFT network, which processes over 42 million messages daily as of 2026, according to SWIFT. You’ll typically see them in trade finance, standby letters of credit, and pre-advice scenarios.
When Should You Use MT199 vs. MT799?
MT199 works best when you need to:
- Confirm a bank’s readiness to proceed with a transaction
- Share specifics like bond value or SKR confirmation
- Coordinate between banks before issuing formal instruments
MT799 comes into play when you must:
- Prove a buyer has enough funds for a trade
- Prepare for a letter of credit or documentary credit
- Get an authenticated confirmation of available liquidity
Here’s the catch: An MT799 marked “RWA” (Ready, Willing & Able) doesn’t lock funds. It’s just a statement of capability—not a lien or hold.
How Do You Send an MT199? (Step-by-Step for 2026 SWIFT Interface)
Assuming you’re using SWIFT Alliance Web Platform (version 7.4 as of 2026), here’s how:
- Log In: Access SWIFT Alliance Web at
https://allianceweb.swift.comwith your Institution Code and Operator Certificate. - Pick the Message Type: Go to Messages → Create New → MT Series and choose MT199 from the list.
- Fill the Header:
- Sender BIC: Your bank’s 8- or 11-character SWIFT BIC (e.g., CHASUS33).
- Receiver BIC: The counterparty bank’s SWIFT BIC.
- Priority: Choose Normal unless it’s high-value (then pick Urgency: High).
- Write the Message: Use free text to explain the purpose. For example:
2026-04-05 | Ready to proceed with SKR confirmation for USD 5,000,000.00. Confirm receipt and readiness to advance.
- Add a Reference (Optional): Put the contract or LOI number in Field 21 if needed.
- Send It: Click Validate to check syntax and authentication, then hit Send. SWIFT will encode it with your bank’s test key automatically.
What If Sending an MT199 Fails?
When MT199 hits a snag, don’t panic. Try these fixes:
- Switch to MT799 for Proof of Funds: If you need to verify funds, MT799 works similarly. Just make sure Field 70 says: “Proof of funds for [amount] in [currency] as of [date].”
- Use Pre-Advice (MT103/202): If MT199 gets ignored, have the sending bank issue an MT202 (financial institution transfer) or MT103 (customer transfer) with: “Pre-advice of incoming USD 5M on [date].”
- Call SWIFT Support: Messages timing out or failing authentication? Reach SWIFT Global Support at +32 2 655 31 31 (24/7). Bring your SWIFT Reference Number (SRN) from the logs.
How Can You Prevent MT199/MT799 Issues?
To keep things smooth:
- Double-Check BICs: Use SWIFT’s BIC Directory (https://www.swift.com/bsd) to confirm counterparty BICs before hitting send.
- Keep Messages Clear: Make Field 70 (Transaction Details) straightforward. Skip jargon like “SKR” unless both sides already agree on it.
- Handle Test Keys Properly: MT799 needs active test key exchange. Have your SWIFT Operations team check key validity every quarter.
- Log Everything: Keep records of sent MT199/MT799 messages with timestamps and acknowledgments. It’s a lifesaver for audits and disputes.
One last thing: Neither MT199 nor MT799 moves money. They’re just tools for communication. Always follow up with a formal instrument (like an SBLC via MT760 or LC via MT700) for binding commitments.
