MT-760 Standby Letter of Credit: Complete Guide

An MT-760 Standby Letter of Credit is a bank undertaking transmitted over SWIFT. If the applicant fails to perform, the issuing bank pays the beneficiary against a compliant demand, up to the stated amount, before expiry and under the agreed rule set. Used correctly, an MT-760 SBLC unlocks shipment, secures EPC obligations, satisfies tender requirements, and supports structured credit. Used without proper preparation, it becomes a slow cycle of rejected wording, compliance delays, and last-minute amendments.

This guide covers how MT-760 works, what the SWIFT fields mean, which rule sets apply, what banks underwrite, how the issuance sequence runs, and the most common reasons deals fail. For SBLC pricing specifically, see how SBLC costs are calculated.

What Is an MT-760 SBLC?

MT-760 is the SWIFT FIN message category used to issue a demand guarantee or standby letter of credit. It creates an authenticated, bank-to-bank record and standardises key fields so advising banks can verify and transmit the undertaking. The legal enforceability does not derive from the fact that it travels over SWIFT. It derives from the fact that it is a contractual bank undertaking governed by a recognised rule set and the governing law stated in the instrument.

The SBLC is a secondary payment mechanism: it pays only if the applicant fails to perform the underlying obligation. This distinguishes it from a documentary credit, which is the primary payment mechanism in a trade transaction.

MT-760 SWIFT Field Structure

Understanding the key fields in an MT-760 message helps both applicants and beneficiaries verify the instrument and avoid the most common drafting errors that result in discrepant demands or non-acceptance by advising banks.

Field :50:(Applicant) and :59:(Beneficiary) must match corporate registry records and the names used in the underlying contract exactly. Discrepancies here are the single most common cause of advising bank refusals. Field :72Z: contains the demand conditions — these must be objective, specific, and achievable in practice, not aspirational.

Rule Sets: ISP98, UCP 600, and URDG 758

The rule set governs how the SBLC operates, how demands are examined, and what constitutes a complying presentation. Selecting the wrong rule set creates ambiguity that benefits neither party.

MT-760 vs MT-799 vs MT-700

These three message types are consistently confused, particularly by parties who have not worked directly in SWIFT issuance sequences. Confusing a non-binding pre-advice with a binding instrument is a common source of disputes and fraud.

Where MT-760 SBLCs Are Used

The most effective use cases share the same foundation: a real contract, a real counterparty, and a clearly defined risk that the SBLC addresses. The instrument sits inside a broader structure that includes KYC, sanctions screening, and documentary controls.

Issuance Sequence: From Mandate to MT-760

A controlled workflow reduces back-and-forth and keeps the instrument aligned with the underlying deal timetable. The best outcomes come from a single thread of control: one package, one draft, one issuer process, tracked to a real deadline.

What Banks Underwrite Before Issuance

Banks underwrite repayment capacity, controllability, and compliance. If any of those fall short, pricing increases, the limit shrinks, or the file is declined. There is no workaround for a weak credit profile.

• Applicant credit including financial statements, cash generation, leverage profile, and banking history.
• Transaction logic including the underlying contract, counterparty strength, and performance timetable.
• Collateral and controls such as cash cover, pledged deposits, receivables assignment, inventory controls, or other security packages.
• Jurisdiction and enforceability including governing law, courts, and the beneficiary bank's confirmation policy.
• KYC, AML, and sanctions covering ownership, directors, counterparties, routes, goods, and payment chain.

Drafting That Prevents Re-Issues

Draft quality determines speed. The most common failures are avoidable: mismatched legal names, unclear expiry mechanics, conflicting rule language, and demand requirements that cannot be satisfied in practice.

• Applicant and beneficiary names must match corporate registry records and contract party names exactly.
• Rule set selection must be explicit — ISP98, UCP 600, or URDG 758 — and not mixed in drafting language.
• Expiry logic must cover the full performance window plus a buffer, with clean extension mechanics if needed.
• Governing law and jurisdiction should be practical for enforcement and compatible with the beneficiary bank's confirmation appetite.
• Demand requirements should be tight, objective, and achievable — not a free-form statement that raises issuer concerns.

Cost Drivers and Economics

Pricing is driven by credit risk, jurisdiction, tenor, beneficiary requirements, and whether confirmation is needed. In most mandates, the economics fall into four components: issuing bank commission (quoted per annum on the face amount), fixed issuance and amendment charges, confirmation pricing where required, and professional costs for legal review or opinion.

Document Requirements Checklist

An issuer-ready file contains what compliance and credit teams need to approve, not what sales decks prefer to show. Incomplete files are the single largest source of delays.

• Executed underlying contract referencing the required security instrument and the performance obligations it covers.
• Corporate registry extracts, ownership structure, director information, and authorised signatory evidence for all parties.
• Audited financial statements and latest interim management accounts for the applicant.
• Beneficiary bank details, BIC, and any beneficiary bank confirmation policy or pre-approval requirements.
• Draft SBLC wording including call conditions, expiry date, extension mechanics, and rule set reference.
• Completed KYC, AML, and sanctions questionnaire with supporting documentation.

Common Deal Breakers

• Sanctions exposure in counterparties, routes, goods categories, or the payment chain.
• Beneficiary structures that are unclear, subject to change, or not commercially justified by the underlying transaction.
• Expiry windows that do not cover the real performance period or relevant shipment timeline.
• Demand requirements that are overly broad, subjective, or inconsistent with the chosen rule set.
• Applicants seeking an SBLC to support a third party's borrowing without enforceable reimbursement controls in place.
• Applicant financials that do not demonstrate capacity to reimburse a called instrument.

MT-760 SBLC FAQ

MT-760 Arrangement Service

Financely runs the process from structuring to execution through regulated counterparties. The engagement focuses on speed and certainty: clean drafting, issuer alignment, credit strategy for limited collateral, and an execution workflow that stays controlled from mandate to SWIFT transmission. If your structure does not rely on full cash collateral, we bring options that can close the gap, including lender-recognised controls and, where appropriate, private credit participation.

Disclaimer: This page is for general information only and does not constitute legal, tax, regulatory, investment, or credit advice. Financely is not a bank and does not issue letters of credit or guarantees. Any SBLC, documentary credit, confirmation, or financing facility is provided solely by regulated counterparties under their own licences, approvals, documentation, and credit decisions. All mandates are subject to eligibility, full KYC and AML review, sanctions screening, and execution of formal agreements. SBLCs are contingent liabilities and may become a reimbursement obligation if a compliant demand is honoured by the issuing bank.

↑