MT760 Standby Letter of Credit
Trade Finance Instruments

MT760 SWIFT Message and the Standby Letter of Credit

The phrase “MT760” is often used incorrectly in international deals. MT760 is not a product you buy. It is a SWIFT message type banks use to transmit a guarantee or standby undertaking to another bank for advising or issuance workflow.

A Standby Letter of Credit is the instrument. MT760 is a bank to bank delivery format commonly used to transmit that instrument through authenticated channels.

What a Standby Letter of Credit Is

A Standby Letter of Credit (SBLC) is a contingent payment undertaking issued by a bank in favour of a beneficiary. It supports a defined underlying obligation such as payment for goods, performance under a contract, advance payment support, lease obligations, or project performance security.

The enforceability comes from the SBLC text, the governing rules stated in the instrument (often ISP98 or UCP 600), and the governing law and jurisdiction. The message format is not the legal foundation.

What MT760 Actually Does

MT760 is a structured SWIFT FIN message used between banks involved in the issuance of a guarantee or standby. In common flows, the issuing bank sends MT760 to the beneficiary’s advising bank. The advising bank authenticates the SWIFT message and advises the beneficiary.

Issuance and Advice

Issuing bank transmits the undertaking to an advising bank via MT760. The advising bank confirms authenticity and advises the beneficiary based on that transmission.

Why Banks Use It

SWIFT provides authentication and message integrity. It is an operational control that reduces disputes over whether an instrument was actually issued.

What It Contains

Core data including references, applicable rules, and the undertaking wording or key terms. Some banks use extension messaging for longer text where needed.

What It Does Not Do

MT760 is not a proof of funds, not a settlement mechanism, and not a payment instruction. It carries an undertaking, not cash.

Typical MT760 Workflow

  1. Applicant and beneficiary agree the commercial contract terms and required standby wording.
  2. Applicant’s bank underwrites the applicant, approves collateral and conditions, then issues the SBLC.
  3. Issuing bank transmits the undertaking bank to bank via MT760 to the advising bank (often the beneficiary’s bank).
  4. Advising bank authenticates and advises the beneficiary, typically providing an advice letter and the SBLC text.
  5. If amendments are required, banks use amendment and acknowledgement flows (commonly handled via related category 7 message types).

MT760 vs Other SWIFT Messages You Will See in Practice

Some transactions use preliminary messaging before MT760 issuance. This is common where counterparties want early confirmation of bank intent before final wording and issuance conditions are satisfied.

MT799 Pre-Advice

A free-format message sometimes used to communicate intent or preliminary information. It is not a substitute for an issued SBLC.

MT767 Amendment

Used to amend an undertaking after issuance, for example to extend expiry, adjust amount, or update wording.

MT768 Acknowledgement

Used in acknowledgement flows between banks to confirm receipt or action within the guarantee or standby messaging chain.

MT769 Reduction or Release

Used to advise reduction in amount or release of the undertaking when conditions are satisfied.

Alternative Delivery Methods for a Standby Letter of Credit

While SWIFT MT760 is common for bank to bank transmission, alternative delivery methods exist. The correct method depends on the beneficiary’s requirements, the issuing bank’s processes, and local market practice.

Paper SBLC Issued and Couriered

Some banks issue the SBLC as a signed paper instrument delivered by secure courier. The beneficiary may still require their bank to verify the issuer before acceptance.

Direct Bank to Bank Advice via SWIFT to Beneficiary Bank

The standard approach in many cross-border transactions: issuance via MT760 to the beneficiary’s bank for advice, with authentication performed by the receiving bank.

Counter-Undertaking and Local Undertaking

In some jurisdictions, a local bank issues the local standby or guarantee supported by a counter-undertaking from a foreign bank. This can reduce enforceability and jurisdictional friction for the beneficiary.

Bank Authenticated Copies for Review

Drafts and authenticated advices can be provided for review, but acceptance should rely on bank-authenticated channels. Screenshots and forwarded emails are not a verification method.

A common failure mode is accepting “swift copy” screenshots or third-party PDFs as proof of issuance. If an SBLC is real, the beneficiary’s bank can verify it through authenticated bank to bank channels.

Practical Points Beneficiaries and Sponsors Should Clarify Early

  • Applicable rules: confirm whether the standby is governed by ISP98 or UCP 600 and ensure the contract aligns.
  • Beneficiary bank details: the issuing bank will often require correct advising bank coordinates and routing instructions.
  • Expiry and claim conditions: ensure the standby terms match the underlying commercial risk, including the presentation requirements.
  • Confirmation requirement: if the beneficiary requires confirmation, address it early because it affects pricing, bank selection, and conditions.
  • Jurisdiction and enforceability: align governing law and forum expectations with the beneficiary’s enforcement needs.

Request Indicative SBLC Arrangement Terms

If you need an SBLC for a real transaction, submit your contract context, required wording, amount, beneficiary details, and timeline. We will respond with indicative terms subject to underwriting, KYC and AML, and partner approvals.

Disclaimer: This page is for general information only and does not constitute legal advice or a commitment to issue any financial instrument. Financely is not a bank. All issuance, confirmation, and credit decisions remain with regulated banking partners and are subject to underwriting, KYC and AML, sanctions screening, and legal documentation.