MT799 SWIFT Message: The Complete Guide for Trade Finance Professionals
The MT799 is one of the most discussed and most misunderstood messages in trade finance. It appears in legitimate transactions as an authenticated bank-to-bank coordination tool before a formal instrument is issued. It also appears in fraudulent pitches as a fake proof of funds product, a monetisable asset, and a yield generator.
This guide explains exactly what the MT799 is, what it is not, when it is legitimately used, how it fits in the SWIFT message sequence, and what templates for each use case look like. If you are working on a transaction that involves an MT799, this is the reference you need.
Contents
- What Is the MT799
- SWIFT Category 7 and Where MT799 Sits
- What the MT799 Does and Does Not Do
- MT799 vs MT760: The Critical Distinction
- The SWIFT Message Sequence in a Trade Transaction
- Legitimate Uses of MT799
- MT799 Templates for Each Use Case
- MT799 Field Structure Explained
- MT799 Fraud: How to Recognise It
- How to Verify an MT799
1. What Is the MT799
The MT799 is a SWIFT Category 7 free-format message. It is used by banks to communicate with other banks in an authenticated, documented way before a formal financial instrument or payment is transmitted. The message has no fixed content structure. The bank drafts the text of the message according to the specific purpose of the communication, which is why it is called a free-format message.
The authentication is the critical feature. Because the MT799 travels over the SWIFT network between two financial institutions with valid BIC codes and an active RMA relationship, the receiving bank knows with certainty who sent it, when it was sent, and that it has not been altered in transit. This makes it categorically different from an email, a PDF, or any other form of off-network communication claiming to represent a bank's position.
The MT799 belongs to SWIFT's Category 7 message family, which covers documentary credits and guarantees. Other Category 7 messages include the MT700, used to issue a documentary letter of credit, and the MT760, used to issue a standby letter of credit or bank guarantee. The MT799 is the communication layer within that family, used to coordinate and confirm before those binding instruments are transmitted.
Key fact: The MT799 is a bank-to-bank message only. It travels between SWIFT member institutions with valid BIC codes. A corporate entity, broker, or private individual cannot send or receive an MT799 directly. If someone claims to hold, control, or transmit an MT799 on behalf of a bank without being a bank themselves, that claim is not credible.
2. SWIFT Category 7 and Where MT799 Sits
SWIFT messages are organised into categories numbered 1 through 9 based on their function. Category 7 covers documentary credits, guarantees, and standby letters of credit. Every message type in Category 7 relates in some way to the issuance, amendment, or communication around these instruments.
| Message Type | Function | Binding? |
|---|---|---|
| MT700 | Issue of a Documentary Credit. The formal issuance of a letter of credit by the issuing bank to the advising bank. Specifies all payment conditions, document requirements, and parties. | Yes. Creates a binding payment obligation subject to UCP 600 document compliance. |
| MT705 | Pre-Advice of a Documentary Credit. Notifies the advising bank that a full MT700 is forthcoming. Provides early visibility of the credit before the full instrument is transmitted. | No. Pre-advice only. The MT700 is the binding instrument. |
| MT707 | Amendment to a Documentary Credit. Conveys amendments to the terms of a previously issued MT700. | Yes, once accepted by all parties per UCP 600. |
| MT760 | Guarantee or Standby Letter of Credit. Issues a bank guarantee or SBLC in favour of the beneficiary. The issuing bank makes a binding payment undertaking. | Yes. Creates a legally enforceable payment obligation under URDG 758 or ISP98. |
| MT767 | Guarantee or Standby Letter of Credit Amendment. Conveys amendments to a previously issued MT760. | Yes, once accepted. |
| MT799 | Free Format Message. Bank-to-bank communication of any content related to Category 7 instruments. Used for pre-advice, proof of funds statements, coordination, and confirmation of intent before binding instruments are issued. | No. Non-binding unless the specific text of the message constitutes a legal commitment under applicable law, which is rare and context-specific. |
3. What the MT799 Does and Does Not Do
The confusion around MT799 in trade finance circles stems almost entirely from a misunderstanding of what the message can and cannot do. The list below is definitive.
What MT799 Does
Provides authenticated, tamper-evident bank-to-bank communication over the SWIFT network.
Confirms that a bank is aware of and engaged with a specific transaction before a binding instrument is issued.
Communicates a bank's readiness or intent to issue an SBLC, bank guarantee, or LC once defined conditions are met.
Conveys a bank's statement that client funds of a specified amount are available for a defined purpose.
Aligns transaction references, BIC codes, and sequence numbers between the sending and receiving bank before final instrument transmission.
Provides the receiving bank with comfort that a counterparty bank is credible and engaged, which can accelerate the receiving bank's own compliance and credit process.
What MT799 Does Not Do
It does not transfer funds. No money moves when an MT799 is sent.
It does not create a binding payment obligation or guarantee. The text is informational, not contractual, unless specific language creates a commitment under applicable law.
It does not block or ring-fence funds. A funds availability statement in an MT799 does not prevent those funds from being deployed elsewhere.
It does not constitute a letter of credit, a bank guarantee, or an SBLC. Those require MT700 or MT760 respectively.
It is not a substitute for due diligence. An MT799 from a counterparty bank does not remove the receiving bank's obligation to conduct KYC and credit assessment.
It cannot be sent by a non-bank entity. Brokers, corporates, and private individuals have no access to the SWIFT network for Category 7 messaging.
4. MT799 vs MT760: The Critical Distinction
The MT799 and MT760 are the two SWIFT Category 7 messages most commonly referenced in trade finance transactions involving SBLCs and bank guarantees, and they are the two most frequently confused. The distinction is fundamental and not subtle.
| Factor | MT799 | MT760 |
|---|---|---|
| Nature of message | Free-format communication. Non-binding. Informational. | Formal instrument issuance. Binding. Creates legal obligations. |
| Effect on funds | None. No funds are moved, blocked, or committed. | The issuing bank ring-fences capacity and creates an enforceable payment undertaking. |
| Legal standing | Generally not legally binding unless specific commitment language is used and accepted under applicable law. | Legally binding under URDG 758 (guarantees) or ISP98 (SBLCs). Enforceable in courts in signatory jurisdictions. |
| Bank cost | Typically no fee, or a minimal administrative charge. | Issuance fee typically 1 to 2 percent per annum of the face value, plus applicable bank charges. |
| When sent in sequence | Before the MT760. Used to confirm readiness and align references. | After the MT799 pre-advice. The operative instrument that activates the guarantee or SBLC. |
| Beneficiary reliance | Beneficiary receives notice of intent but cannot draw on an MT799. It is not a payment instrument. | Beneficiary can draw on the SBLC or guarantee by presenting a compliant demand under the terms of the MT760. |
| Who can send | SWIFT member banks with a valid RMA link to the receiving bank. | SWIFT member banks with a valid RMA link to the receiving bank. Additional credit and compliance requirements apply before issuance. |
The rule: MT799 is talk. MT760 is action. A transaction that relies on an MT799 as the final instrument has not completed. The MT799 is a step in the sequence, not the destination. Any party asking you to rely on an MT799 as if it were equivalent to an issued SBLC or bank guarantee is either confused or misleading you.
5. The SWIFT Message Sequence in a Trade Transaction
In a transaction involving an SBLC or bank guarantee as credit enhancement, the MT799 typically appears as one step in a defined sequence. Understanding where it sits in that sequence clarifies both its function and its limitations.
- Step 1: Commercial agreement. Buyer and seller agree terms. The seller requires a bank guarantee or SBLC as security before performing. The buyer instructs their bank to begin the issuance process.
- Step 2: KYC and compliance. The issuing bank conducts know-your-customer and anti-money-laundering checks on the applicant and the transaction. Sanctions screening of all parties and jurisdictions is completed. This step must be complete before any SWIFT message is sent.
- Step 3: MT799 pre-advice. Once compliance is satisfied and credit approval is obtained, the issuing bank sends an MT799 to the beneficiary's bank confirming readiness to issue the instrument and providing key transaction references. This allows the beneficiary's bank to begin its own internal review and align on the terms before the binding instrument arrives.
- Step 4: MT760 issuance. The issuing bank transmits the MT760 containing the full text of the SBLC or bank guarantee to the advising or confirming bank. The instrument is now live and the beneficiary can rely on it.
- Step 5: MT700 issuance, if applicable. If a documentary LC is also part of the transaction, the issuing bank transmits the MT700 to the advising bank once the SBLC is in place and any remaining conditions are satisfied.
- Step 6: Trade execution and settlement. Goods are shipped, documents are presented, and payment is made via MT103 wire transfer or by drawing under the documentary credit.
The MT799 in context: In a well-run transaction, the MT799 is a relatively routine step. It is not a milestone in itself. Its presence tells the beneficiary's bank that the issuing bank is engaged and ready to move. Its absence in situations where parties have asked for it as a condition may indicate that the issuing bank has not yet completed its compliance process or has not obtained the necessary credit approvals, which is useful information for the receiving side of the transaction.
6. Legitimate Uses of MT799
There are four distinct contexts in which an MT799 is legitimately and commonly used in trade and structured finance transactions.
Pre-Advice of Instrument Issuance
The issuing bank sends an MT799 to the beneficiary's bank to confirm that an SBLC, bank guarantee, or documentary LC will be issued shortly. Gives the receiving bank early visibility to begin internal processing, compliance review, and RMA verification before the binding MT760 or MT700 arrives. Reduces the time between instrument issuance and the beneficiary being able to rely on it.
Proof of Funds Confirmation
A bank sends an MT799 to a counterparty bank confirming that a client has funds of a specified amount available for a defined transaction purpose. Used in commodity trades, project finance transactions, and structured deals where the counterparty requires bank-authenticated evidence of the buyer's or borrower's financial capacity before committing to performance. Not a block on funds unless combined with a separate escrow or blocking arrangement.
Transaction Reference Alignment
In complex multi-bank transactions, the MT799 is used to align reference numbers, BIC codes, value dates, expiry mechanics, and instrument terms between the sending and receiving banks before the binding instruments are issued. This prevents mismatches in subsequent MT760 or MT700 messages that would require amendment and cause delay. Particularly important in back-to-back LC structures and multi-corridor transactions.
Ready, Willing, and Able Confirmation
In some structured transactions, particularly in commodity and project finance, a bank is asked to confirm its client's readiness, willingness, and financial ability to proceed with a defined transaction. The RWA confirmation sent via MT799 serves as authenticated bank-level verification of client status before contracts are executed or performance obligations are triggered. Not a guarantee of performance, but a formal bank-level statement that the client has the capacity to proceed.
7. MT799 Templates for Each Use Case
Because the MT799 is a free-format message, there is no single mandated template. The following examples represent the structure and content of legitimate MT799 messages for each of the four use cases above. All variable fields are indicated in brackets. These templates are reference guides for understanding what a genuine MT799 looks like, not documents for use without bank review and issuance.
Template 1: Pre-Advice of SBLC Issuance
Template 2: Proof of Funds Confirmation
Template 3: Ready, Willing, and Able (RWA) Confirmation
Template 4: Transaction Reference Alignment
8. MT799 Field Structure Explained
While the MT799 is a free-format message, it does follow a defined SWIFT field structure. Understanding the field codes helps verify that a message is structured correctly and has been transmitted through the SWIFT network rather than fabricated outside it.
| Field Tag | Field Name | Description |
|---|---|---|
| :20: | Transaction Reference Number | Unique alphanumeric reference assigned by the sending bank to identify this specific message. Must be unique within the sending bank's system. Used for cross-referencing in subsequent messages. |
| :21: | Related Reference | Reference to a related transaction, application, or earlier message. Used to link the MT799 to the underlying transaction or to a prior communication in the same sequence. |
| :79: | Narrative | The free-format text body of the message. All substantive content, including the confirmation, proof of funds statement, or pre-advice text, is contained in this field. Maximum 35 characters per line. No fixed format imposed by SWIFT beyond the character limit. |
SWIFT header blocks: Every MT799 also contains standard SWIFT header blocks that are not visible in the message body text but are embedded in the transmission. These include Block 1 (the basic header identifying the SWIFT service and the sender's BIC), Block 2 (the application header identifying the message type and receiver's BIC), and Block 3 (user header with optional reference fields). A genuine MT799 received by a bank through the SWIFT network will have these headers verified automatically. A PDF or email copy does not have them.
9. MT799 Fraud: How to Recognise It
The MT799 is one of the most commonly referenced instruments in trade finance fraud. Its name is technical enough to sound credible, its free-format nature means that fraudulent versions are easy to fabricate, and its association with large transactions makes it an effective prop in schemes targeting businesses and individuals with significant capital.
The fraud patterns cluster into a small number of recurring types. Recognising any one of them should terminate further engagement.
The MT799 as a Monetisable Asset
The claim that an MT799 itself is an instrument that generates yield, can be monetised, leased, or used as collateral for a credit facility. An MT799 is a communication message. It has no face value, no maturity date, and no claim on any asset. It cannot be monetised or leased. Any offer structured around monetising an MT799 is fraudulent.
PDF and Screenshot Copies
A broker or counterparty provides a PDF, screenshot, or email copy of an alleged MT799 as proof of a bank commitment. Genuine MT799 messages exist on the SWIFT network between two banks. They are not forwarded by email or provided as PDF attachments by intermediaries. Any MT799 presented in this form cannot be verified and should not be relied upon.
MT799 as a Standalone Deal Trigger
The claim that the receipt of an MT799 alone is sufficient to trigger a large payment, credit release, or goods delivery. In a legitimate transaction, an MT799 is a pre-advice or coordination message, not a binding commitment. No responsible party releases funds, goods, or title documents solely on the basis of an MT799.
Upfront Fees to Receive an MT799
The request for an upfront payment, often described as a compliance fee, bank facilitation fee, or verification charge, to trigger the sending of an MT799 from a bank. Banks charge fees for instrument issuance, not for free-format communication messages. A request for an upfront fee to receive an MT799 is a standard advance fee fraud pattern.
Non-Existent Issuing Banks
An MT799 purportedly from a bank whose BIC code does not exist in the SWIFT BIC directory, whose name does not appear in any regulatory register, or whose address and contact details cannot be independently verified. Real banks exist. They have verifiable BIC codes, regulatory registrations, and physical presences. Checking the BIC code in the SWIFT directory is the first and simplest verification step.
Blocked Funds via MT799
The claim that funds have been blocked, ring-fenced, or escrowed through the transmission of an MT799. An MT799 does not block funds. Funds can only be blocked through a formal escrow arrangement or through the specific mechanics of a recognised blocking structure at the bank. An MT799 that claims to have blocked funds is making a statement the message type cannot support.
The clearest rule: A genuine MT799 travels between two SWIFT member banks with valid BIC codes over the SWIFT network. It is never forwarded by a broker, never provided as a PDF attachment, never offered as a product for sale or lease, and never requests an upfront fee. If any of these conditions apply to an MT799 you have been shown, you are looking at a fraudulent document.
10. How to Verify an MT799
If you are the beneficiary's bank or a party whose bank has received an MT799, verification is straightforward because the SWIFT network provides the authentication automatically. The receiving bank's SWIFT interface confirms the sending bank's BIC, the transmission timestamp, and the message integrity. No external verification is required for a message received through the SWIFT network.
If you are a corporate counterparty who has been told that an MT799 has been sent to your bank, the correct verification route is to contact your bank's trade finance department and ask them to confirm receipt. Your bank will be able to confirm whether an MT799 matching the described transaction has been received from the claimed sender. Do not rely on a copy provided by a broker or counterparty as evidence of transmission.
- Verify the BIC code. Check the sending bank's BIC code against the SWIFT BIC directory. Every legitimate SWIFT member institution has a registered, searchable BIC. An unrecognised BIC code is an immediate red flag.
- Check reference number consistency. The reference number in field :20: should be consistent across all related messages. If reference numbers change between the MT799 and the subsequent MT760 or MT700, this indicates either an administrative error or a fabricated document chain.
- Confirm through your own bank. Ask your bank's trade finance team to confirm receipt of the MT799 directly through their SWIFT interface. Do not accept a third-party confirmation as a substitute.
- Do not rely on PDF copies. A PDF or printed copy of an alleged MT799 has no evidentiary value and cannot be authenticated. The message must be verified through the receiving bank's SWIFT records.
- Verify the sending bank independently. Confirm that the sending bank is a regulated institution by checking the relevant banking regulator's register in the bank's stated jurisdiction. A bank that cannot be found in its regulator's register is not a legitimate SWIFT member.
Working on a Transaction That Involves an MT799?
If you are structuring a trade finance or structured lending transaction and need guidance on the correct SWIFT message sequence, instrument selection, or bank introduction for a legitimate MT799 and MT760 process, submit your deal through our request for quote page. We work with regulated banks and specialist trade finance lenders across the instruments described in this guide.
Frequently Asked Questions
The most common questions about MT799 from trade finance practitioners and corporate clients.
What is an MT799 SWIFT message?
A free-format SWIFT Category 7 message used for authenticated bank-to-bank communication. Used to confirm intent, communicate proof of funds, or coordinate transaction references before a binding instrument such as an MT760 SBLC is issued. It is not a payment instruction and does not transfer funds.
What is the difference between MT799 and MT760?
MT799 is non-binding communication. MT760 is a binding instrument that issues an SBLC or bank guarantee and creates a legally enforceable payment undertaking. MT799 typically precedes MT760 as a pre-advice. Relying on an MT799 as if it were equivalent to an MT760 is a fundamental misunderstanding of both messages.
Can a corporate send an MT799?
No. MT799 is a bank-to-bank message transmitted over the SWIFT network. Only SWIFT member institutions with valid BIC codes and active RMA relationships can send and receive MT799 messages. Brokers, corporates, and private individuals cannot send an MT799.
Does an MT799 prove funds exist?
An MT799 can contain a bank's statement that client funds are available for a specific purpose. It does not block or ring-fence those funds. It is a bank's authenticated statement at a point in time, not an irrevocable commitment to make those funds available indefinitely.
What are the signs of MT799 fraud?
Claims that an MT799 is a monetisable asset. PDF copies presented by brokers as proof of a bank commitment. Requests for upfront fees to trigger an MT799 transmission. Claims that an MT799 has blocked or ring-fenced funds. BIC codes that do not appear in the SWIFT directory. Any one of these is sufficient to terminate engagement.
How do I verify an MT799 I have been told about?
Contact your bank's trade finance department and ask them to confirm receipt through their SWIFT interface. Verify the sending bank's BIC code in the SWIFT BIC directory. Check the sending bank's regulatory registration. Do not rely on PDF copies, email forwards, or broker-provided documentation as verification.
Disclaimer: This guide is informational and does not constitute legal, financial, or investment advice. SWIFT message types, their legal standing, and their application in specific transactions vary by jurisdiction, transaction type, and the terms of the underlying commercial agreements. MT799 templates provided in this guide are illustrative reference examples only and should not be used without review and issuance by a qualified banking institution. Obtain independent legal and banking advice before relying on any SWIFT message in a commercial transaction.