Standby Letters of Credit (SBLCs) and Bank Guarantees (BGs) are vital tools in international trade and project finance. When issued correctly, they provide an independent payment guarantee from a bank. The issuing bank’s obligation is separate from the underlying contract, ensuring security and transparency for both sides.
These instruments are governed by the International Chamber of Commerce (ICC) through two key frameworks: the Uniform Customs and Practice for Documentary Credits (UCP 600) and the Uniform Rules for Demand Guarantees (URDG 758). Both set global standards for documentation, messaging, and compliance (source: ICC Academy, Investopedia).
However, the private market is often crowded with intermediaries who promote unverified procedures, ignore compliance, and expose clients to unnecessary financial risks.
Understanding Verified Receivers
In our recent article, Understanding Verified Receivers: Rethinking Trust in Large Bank-to-Bank Transfers, we explained that a verified receiver is a regulated institution or corporation that has passed full KYC/KYB checks. Funds from such entities move through official banking systems like SWIFT, RTGS, or correspondent networks.
Verification is not optional. It protects all parties, ensures compliance with global standards, and upholds financial integrity.
A Real-World Example: Requests That Bypass Compliance
Recently, a prospective client reached out to us with what seemed like a straightforward proposal. They wanted to “present procedures to a provider” and shared a generic PDF with the following structure:
- The provider’s bank would send a SWIFT MT799 message confirming readiness.
- The beneficiary’s bank would then issue a SWIFT MT760 performance guarantee.
- The provider’s bank would issue the actual SBLC via MT760.
- Payment would follow after issuance.
When we requested further details such as the issuing bank’s name, instrument type, and compliance documents, the reply was vague. It mentioned RMA relationships and one billion euros in tranches but included no verified bank name or proof of funds.
This structure was not only unclear but also non-compliant with established SWIFT and ICC procedures.
Why This Procedure Is Problematic
1. Misuse of SWIFT messages
The MT799 message is a free-format communication used to confirm fund readiness. It is not a payment or guarantee instrument (source: LetterOfCredit.biz). Legitimate banks issue SBLCs using the MT760 message, which transfers the guarantee obligation. A proper transaction starts with an MT799 pre-advice and ends with an MT760 issuance. Any procedure that reverses this order introduces unnecessary risk.
2. Missing compliance documents
International standards require banks to verify customers and beneficial owners before any transaction. This includes identifying the source of funds (where the money originates) and the source of wealth (how the client accumulated it). Proposals that lack these documents should never proceed (source: ComplyAdvantage, BIS).
3. No reference to governing rules
Under UCP 600, banks that issue letters of credit must explicitly include the rules in the contract. These standards apply in more than 175 countries. Similarly, URDG 758 ensures transparency, risk reduction, and legal certainty. Procedures that ignore these frameworks compromise the independence and validity of the SBLC.
Due diligence is not just formality. It is a shield against fraud, sanctions risk, and reputational damage. As the Basel Committee notes, banks should never establish a relationship until a client’s identity and ownership are fully verified (source: Basel Committee on Banking Supervision).
What a Verified Receiver Means at Rani Nexus
At Rani Nexus, a verified receiver is not just a buyer with access to capital. It is a financially regulated entity that meets the same compliance standards banks apply to themselves.
Key criteria include:
- Regulatory status: The receiver must operate under a recognised financial authority.
- KYC/KYB: Full corporate documentation, beneficial ownership proof, and AML screening are mandatory.
- Source of funds: We verify the origin of funds and how the wealth was generated (source: ComplyAdvantage).
- Bank-to-bank communication: All transactions must use official SWIFT channels such as MT799 followed by MT760 or RTGS.
- Governance: Every SBLC must comply with ICC frameworks (source: ICC Academy).
Only when all these conditions are met do we connect verified providers and receivers. Our goal is to bridge both sides and ensure every deal meets institutional standards.
Why Compliance Protects You
Risk mitigation: By following UCP 600 and URDG 758, all parties share a common framework. This clarity prevents disputes and ensures accountability.
Bank confidence: Banks issue SBLCs only when they know the applicant’s credibility. A proper MT799/MT760 sequence demonstrates readiness without exposing funds.
Regulatory protection: AML and KYC compliance prevent penalties, account closures, and reputational harm.
Fraud prevention: Verifying sources of funds and wealth helps detect illicit activities early and safeguards both sides of the transaction.
Our Message to Prospective Clients
We value every inquiry we receive. The trade finance world is complex, and we aim to simplify it for serious professionals. However, if a proposal does not include clear compliance documentation, verified bank details, or alignment with ICC and SWIFT standards, we will not proceed.
If you represent a regulated institution or corporate client with verifiable SBLCs or BGs, we welcome your contact. Rani Nexus acts as an intermediary between legitimate providers and receivers, ensuring every transaction is conducted ethically and transparently.
