MT799 SWIFT Message Meaning
An MT799 SWIFT message is a free-format bank-to-bank message used for authenticated communication between financial institutions. In trade finance, it is often used to communicate transaction status, readiness, proof-of-funds wording, pre-advice language or other narrative information where a more specific SWIFT message type is not being used.
The important point is that MT799 is a communication message. It does not transfer funds. It does not issue a standby letter of credit. It does not create a bank guarantee by itself. It carries text from one bank to another through the SWIFT network.
Its value depends on the exact wording, the sending bank, the receiving bank, the client relationship, the transaction context and the bank policies on both sides.
What MT799 means in practical terms
MT799 belongs to the SWIFT Category 7 message family used around documentary credits and guarantees. It is commonly described as a free-format message because it allows banks to send narrative information that does not fit into a more specific structured message type.
That flexibility makes MT799 useful in trade finance. A bank can use it to confirm procedural readiness, acknowledge a transaction, respond to another bank, pre-advise a future instrument or communicate limited factual information about funds or account standing.
The receiving bank will not treat every MT799 the same way. A vague MT799 has limited value. A carefully worded MT799 from a credible bank, tied to a real transaction and accepted by the receiving bank, can help move a transaction forward.
Is MT799 used for proof of funds?
Yes, MT799 can be used for proof-of-funds communication when a bank is willing to send a bank-to-bank message confirming specific facts about a client’s funds, account standing or readiness for a transaction.
“MT799 proof of funds” is a market phrase. The message itself is still an MT799 free-format communication. The proof-of-funds value comes from the wording inside the message and the credibility of the bank sending it.
A serious proof-of-funds MT799 should identify the bank, client, transaction reference, amount, currency, account or relationship basis where permitted, conditions, validity period and limits of reliance. Banks often use qualified language because they do not want a proof-of-funds message to become an unintended payment undertaking.
What MT799 does and does not do
The table below separates legitimate MT799 use from common market confusion.
| Question | Answer | Practical meaning |
|---|---|---|
| Can MT799 confirm proof of funds? | Yes, if the sending bank agrees to send appropriate wording. | The message can communicate factual bank-to-bank proof-of-funds information. |
| Does MT799 transfer money? | No. | Funds are moved through payment messages and payment rails, not MT799. |
| Does MT799 issue an SBLC? | No. | SBLC or guarantee issuance is typically handled through MT760 or other applicable undertaking messages. |
| Is MT799 legally binding? | It depends on wording, law and bank treatment. | A factual message is different from a binding payment undertaking. |
| Can MT799 be used as pre-advice? | Yes. | It can tell another bank that a formal instrument or action may follow. |
| Can the receiving bank reject or ignore it? | Yes. | The receiving bank must be willing to accept, review and rely on the message. |
MT799 proof of funds in trade finance
MT799 proof of funds is often requested in commodity trading, project finance, acquisition finance, private credit, bank instrument issuance, escrow preparation and large purchase transactions.
The beneficiary or seller may want comfort that the buyer has funds before issuing documents, reserving inventory, signing final contracts or moving to an instrument issuance stage.
The buyer’s bank may agree to send a proof-of-funds MT799 if the client passes internal checks and the wording is acceptable. Some banks will refuse. Others will only send a narrow message with qualified language. That is normal bank risk control.
MT799 versus MT760
MT799 and MT760 are often mentioned together, especially in SBLC and bank guarantee conversations. They play different roles.
MT799 is generally used for bank-to-bank communication, pre-advice, proof-of-funds language or procedural confirmation. MT760 is used for the issue or requested issue of a demand guarantee or standby letter of credit.
That difference matters. An MT799 may say a bank is ready, aware or prepared to proceed. An MT760 is the message type used to issue the undertaking itself when the bank approves issuance and the instrument wording is finalized.
Common MT799 use cases
MT799 appears in serious transactions when counterparties need bank-to-bank confirmation before moving into final execution.
Proof of funds
A bank confirms limited information about funds, account standing or transaction capacity, subject to bank wording and policy.
Pre-advice
A bank communicates that a formal instrument, such as an SBLC or guarantee, may follow after conditions are met.
Readiness to proceed
A bank confirms procedural readiness or willingness to continue with a defined transaction workflow.
Transaction clarification
Banks exchange narrative information where the matter does not fit a more specific SWIFT message format.
What a serious MT799 proof-of-funds message should cover
The exact wording depends on bank policy, but serious proof-of-funds wording usually needs clear transaction discipline.
The message should reference the applicant or account holder, beneficiary or receiving bank where applicable, transaction reference, currency, amount, purpose, validity, conditions, limitations and confirmation basis.
Weak wording creates problems. A message that says “funds are available” without context may be too vague for a seller, lender or beneficiary. A message that sounds like a payment guarantee may be rejected by the sending bank’s compliance or legal team.
Bank policy controls the message
Banks decide what they will and will not say in an MT799. A client cannot force a bank to issue proof-of-funds wording that the bank’s legal, compliance or operations team will not approve.
Most banks will review KYC, AML, sanctions, source of funds, account history, transaction purpose and receiving bank details before sending a message. Some banks may require indemnities, fees, internal approvals or relationship manager sign-off.
This is why serious MT799 work starts with the bank’s acceptable wording. The transaction should be built around what the bank can actually send.
Common red flags
The MT799 market attracts bad information. Buyers and sellers should be cautious with anyone claiming that MT799 is a funding instrument, a transferable payment order, a magic bank guarantee or a guaranteed route to monetization.
Other red flags include fake SWIFT copies, screenshot-only “confirmations,” non-bank senders, unverifiable BIC details, vague receiving bank information, pressure to bypass bank compliance and promises that no KYC or source-of-funds review is needed.
A real MT799 is bank-to-bank communication. The receiving bank can verify it through its own SWIFT operations. Anything else should be treated carefully.
How MT799 fits into a transaction workflow
A clean MT799 workflow usually begins with a signed commercial transaction, agreed bank coordinates and clear wording. The applicant asks its bank whether it can send the message. The bank reviews the request and approves, rejects or edits the wording.
If approved, the sending bank transmits the MT799 to the receiving bank. The receiving bank reviews the message and confirms whether it is sufficient for the next step. That next step may be document release, contract execution, escrow funding, instrument issuance or further bank communication.
The best workflows define the purpose of the MT799 before it is sent. A message requested without a clear commercial purpose usually creates delay.
Where FG Capital Advisors fits
FG Capital Advisors supports structured finance and trade finance transactions where bank communication, proof of funds, SBLCs, guarantees, offtake contracts or capital-provider requirements must be organized into a credible execution file.
For MT799 matters, the work usually involves transaction review, bank wording logic, receiving-bank requirements, proof-of-funds purpose, document sequencing and the broader financing or trade structure.
The objective is to avoid vague SWIFT requests and build a workflow that banks, counterparties and capital providers can understand.
FAQ
What does MT799 mean?
MT799 is a SWIFT free-format message used for authenticated bank-to-bank communication where no more specific SWIFT message type is being used.
Is MT799 used for proof of funds?
Yes. Banks may use MT799 to communicate proof-of-funds wording, subject to their internal policy, client review, acceptable wording and receiving-bank requirements.
Does MT799 move money?
No. MT799 is a communication message. It does not transfer funds.
Is MT799 the same as MT760?
No. MT799 is a free-format communication message. MT760 is the SWIFT message type used to issue or request the issue of a demand guarantee or standby letter of credit.
Can an MT799 prove that funds are real?
It can provide bank-to-bank evidence if the sending bank confirms specific facts and the receiving bank accepts the wording. The message should be verified through bank channels.
Need MT799 Proof-of-Funds Structuring?
FG Capital Advisors can review the transaction context, receiving-bank requirement and proof-of-funds workflow before the SWIFT request is prepared.
Start Client IntakeTransaction takeaway
MT799 is a free-format SWIFT message for bank-to-bank communication. It can be used for proof of funds, pre-advice or transaction confirmation when the bank agrees to send appropriate wording.
The message itself is not money, not an SBLC and not a bank guarantee. The commercial value comes from the sending bank, the wording, the transaction context and the receiving bank’s acceptance.
For serious trade finance and proof-of-funds work, the right question is simple. What must the receiving bank see, what will the sending bank actually say, and what transaction step depends on that message?
Selected reference sources used for background:
