An MT799 SWIFT message is a free-format text communication that one bank sends to another over the SWIFT network, typically to pass information, confirm readiness, or pre-advise a transaction before a formal instrument is issued. It does not move money, create a payment obligation, or guarantee anything on its own. If you are requesting one, your bank’s trade finance desk drafts and transmits it. If you are receiving one as part of a deal, your job is to verify it directly with the sending bank before treating it as meaningful.
What the MT799 Actually Is
The MT799 sits within SWIFT’s Category 7 messages, which cover documentary credits and guarantees. Unlike the structured messages in that category, it is free-format: the sending bank types the content in plain text instead of filling in coded fields. Banks use it to send pre-advice statements, answer compliance questions, clarify terms, or signal that they are prepared to issue a formal instrument once conditions are met.1SWIFT. MT Category 7 Enhancements Overview
What it does not do matters just as much. An MT799 is not a guarantee. It is not a standby letter of credit. It does not block or reserve funds in any account. The common label “proof of funds” is misleading, because the message confirms only that one bank sent text to another bank. Whether the underlying claim in that text is accurate depends entirely on the wording and the credibility of the sending institution. Treating the message as equivalent to a binding instrument is the single most common misunderstanding in this corner of trade finance, and it is the exact confusion that fraud schemes exploit.
MT799 vs. MT760: Which One Does Your Deal Need
If a counterparty, tender document, or contract calls for a bank guarantee or standby letter of credit, what you ultimately need is an MT760, not an MT799. The MT760 is a structured SWIFT message with coded fields defining the parties, the guaranteed amount, expiry dates, claim conditions, and governing rules. When a bank sends an MT760, it is making a binding undertaking to pay the beneficiary if the terms are triggered.
The MT799 is informational. It might say the bank is ready to issue a guarantee, or that the client holds sufficient funds, but the statement itself carries no enforceable obligation. In practice the sequence runs like this: the issuing bank sends an MT799 as pre-advice, signaling intent. If the receiving party and its bank find the terms acceptable, the issuing bank then transmits an MT760 to formalize the guarantee. Skipping straight to an MT760 is possible but uncommon in complex deals where the parties need to negotiate first.
Pre-advice exists because the MT760 is expensive. Issuing one involves substantial bank fees, legal review, and the commitment of the applicant’s credit facility or collateral. The MT799 lets both sides confirm the deal is worth pursuing before anyone commits those resources.
How to Request an MT799 From Your Bank
Your bank’s commercial or trade finance department handles MT799 requests. Before you contact them, gather the following so the request moves without back-and-forth:
- The full legal name on the account and the account number, matching your entity registration exactly.
- The SWIFT/BIC codes for both the sending and receiving banks. Every institution on the SWIFT network has a Business Identifier Code, and the receiving bank needs its own code to accept routing.2SWIFT. Business Identifier Code (BIC)
- The currency and amount, matching the contract or tender requirement exactly. Even a rounding difference can cause the receiving bank’s compliance team to reject the message.
- The transaction or contract reference, so the receiving institution can route the message to the right project manager or officer.
- The desired wording. Because the message is free-format, the text matters, and some government procurement offices specify exact phrasing in their tender documents. Your bank’s trade finance team will draft the final language, but you need to know what the receiving party expects.
Your bank collects this information through its own authorization forms, available through a relationship manager or business banking portal. Expect compliance checks before transmission, which may add a day or two. Banks charge processing fees that vary with institution and complexity, so ask for a quote upfront. A straightforward message costs considerably less than one requiring extensive compliance or legal coordination.
Once the data is entered into the SWIFT terminal, the network routes the message to the receiving bank. Your bank should give you a transmission confirmation or copy as proof the message was sent. One technical point worth knowing: before any SWIFT message can pass between two banks, the receiving institution must have an active Relationship Management Application (RMA) authorization in place for the sender. If no RMA exists, the message is blocked at the network level, which is a common cause of delays with unfamiliar counterparty banks.3SWIFT. RMA and RMA Plus: Managing Correspondent Connections
How to Verify an MT799 You Receive
If an MT799 arrives as part of a contract bid or business deal, verification is the entire point of the message. SWIFT’s authentication confirms only that the message came from a valid SWIFT terminal. It does not verify the truth of the content. A bank can send a perfectly authentic SWIFT message containing claims that turn out to be inaccurate or misleading.
Start by confirming the sending bank’s BIC against SWIFT’s public directory. Then contact the sending bank directly, using contact information you find independently rather than numbers or emails supplied by the party you are dealing with. Ask the bank to confirm three things: that the message was sent on behalf of the named client, that the stated amounts are accurate, and that the bank stands behind the content. If the sending bank will not or cannot confirm those details, the MT799 is worthless no matter how professional it looks.
Loop in your own bank’s compliance department. They can verify the message through SWIFT’s authentication trail and check whether the sending institution has a valid RMA relationship in place.3SWIFT. RMA and RMA Plus: Managing Correspondent Connections In government procurement, this step is where unqualified bidders get filtered out. A legitimate counterparty with real banking relationships will have no trouble producing a verifiable MT799; the ones who resist verification or offer elaborate excuses for delays are the ones to walk away from.
Fraud Signals Around MT799 Offers
The free-format nature of the MT799 makes it a favored tool in financial fraud. Because any bank can send a text message to another bank, bad actors use counterfeit or misleading MT799 messages to create the appearance of financial backing that does not exist. The FBI has issued a specific public warning about schemes involving fictitious standby letters of credit, in which fraudsters cite MT799 and MT760 references to make their pitches look legitimate.4Internet Crime Complaint Center (IC3). FBI Warns of Fraud Actors Scamming Investors Through Fictitious Standby Letters of Credit
Common warning signs the FBI identifies:
- Advance fees required before any funding materializes.
- The MT799 itself being treated as proof that money is available or committed.
- Non-recourse or forgivable loan offers that claim you will not need to repay.
- Pressure to sign a non-disclosure agreement before seeing deal details.
- Frequent use of the term “monetize” to describe converting bank instruments into returns.
- Deals that require you to move money through foreign banks you have no relationship with.
- References to well-known financial institutions without their knowledge or consent.4Internet Crime Complaint Center (IC3). FBI Warns of Fraud Actors Scamming Investors Through Fictitious Standby Letters of Credit
If a pitch combines several of these signals with an MT799 reference, treat the message as marketing rather than finance until independent verification with the sending bank proves otherwise.
Where the MT799 Fits in a Legitimate Deal
In a real procurement or financing transaction, the MT799 is a waypoint. The typical sequence runs from a Ready, Willing, and Able (RWA) letter, in which a bank states in writing that it is prepared to proceed on a client’s behalf, through the MT799 pre-advice, and finally to the MT760 issuance that creates the actual bank guarantee or standby undertaking. Each step has its own compliance review.
Once both parties are satisfied and contracts are signed, the issuing bank transmits the MT760 through SWIFT with all the structured guarantee fields filled in. The guarantee becomes operative and enforceable under whatever rules govern it. The MT799 has done its job and drops out of the picture. It was never meant to be the instrument itself, only the conversation that led to one.