O
OPTKAS SBLC Portal
Institutional Instrument Platform

SBLC Intake & Funding
Orchestration Platform

Submit your Standby Letter of Credit or Bank Guarantee for structured verification, policy review, and funding facilitation — or register your receiving coordinates to accept an SBLC delivery. All on a single institutional-grade platform.

Submit an SBLCReceive an SBLCTrack a CaseMonetize / Fund →
ISSUING SIDE

Submitting an SBLC

You have an SBLC (or are arranging one) and want to bring it into the OPTKAS system for verification, policy review, facility structuring, and funding. You submit the MT760 details, issuing bank BIC, and party names. The system assigns a case number and begins verification.

Begin Intake →
RECEIVING SIDE

Receiving an SBLC

You have been told an SBLC will be delivered to you but you need to provide your receiving bank coordinates before the MT760 can be transmitted. Submit your bank BIC, account details, and delivery preference here. If your bank isn't SWIFT-connected, choose document-only delivery.

Submit Coordinates →
OPERATOR / FUNDER

Monetize an SBLC

An SBLC has been approved and is ready for monetization. Accept it into custody, structure a funding facility, and route the draw to XRPL, Stellar/USDC, a bank wire, or a Centrifuge DeFi pool — all in one guided workflow.

Start Monetization →

How SBLC Issuance Works in This System

STEP 01

Submit Intake Package

Provide instrument details: issuing bank, SWIFT BIC, face value, currency, expiry, applicant, beneficiary, and transferability status. Paste the raw MT760 SWIFT text if available.

STEP 02

Verification & Policy Check

The system verifies the issuing bank is on the approved list, checks expiry runway, validates transferability, and runs sanctions screening. The MT760 is parsed and cross-checked against declared terms.

STEP 03

Compliance Review

KYC/KYB on applicant and beneficiary. Source/use of funds narrative reviewed. Side letters and fee letters checked. Draw conditions summarized.

STEP 04

Facility Structuring

Once approved, a funding facility is created: face value minus haircut = recognized value. Maximum draw amount is set. Chain is assigned (XRPL / Stellar / Wire).

STEP 05

Draw Execution

Draws are requested against the facility. Each draw requires 2-person approval and address validation before settlement executes on-chain or via wire.

STEP 06

Settlement & Evidence

Settlement records are created with transaction hashes. Full audit trail maintained for every state change, decision, and document uploaded throughout the case lifecycle.

How SBLC Delivery Works — & How Counterparties Receive

An MT760 is a bank-to-bank SWIFT message. For it to reach the beneficiary, the issuing bank needs a receiving bank's SWIFT address and account — these are called “receiving coordinates.” Here's how OPTKAS handles each scenario.

WHAT ARE COORDINATES?

To transmit an MT760, the issuing bank needs:

  • Receiving bank SWIFT BIC — 8–11 chars
  • Account / IBAN — at that receiving bank
  • Beneficiary legal name — exact entity
  • Beneficiary address — registered
WHY THEY'RE OFTEN MISSING

The counterparty (beneficiary) may not yet have a regulated bank account with SWIFT connectivity. The deal is agreed in principle but the receiving pathway isn't set up yet. OPTKAS provides 3 ways to handle this without blocking the transaction.

WHAT HAPPENS NEXT

Regardless of which path you choose, the SBLC case is created immediately. A draft delivery sheet is generated at intake. Final coordinates can be supplied before the MT760 transmission deadline — nothing blocks case creation.

A
MT760 DIRECT
Receiving bank confirmed upfront

The beneficiary has a SWIFT-connected bank account. Provide the receiving bank BIC and account number during intake. OPTKAS generates a final delivery sheet immediately. The issuing bank transmits the MT760 directly to the receiving bank. The counterparty receives notification from their own bank — they never need to visit this portal.

✓ Fastest path — no follow-up needed
B
MT799 PRE-ADVICE STAGED
Coordinates pending — staged delivery

Most common path. The case is created with coordinates marked PENDING. A draft delivery sheet is issued to the issuing bank saying “hold MT760 — coordinates incoming.” The counterparty receives a secure portal link and submits their receiving bank details here. Once ops verifies and assigns a bank profile, the case transitions to final — MT799 pre-advice is sent first, then MT760.

⟳ Counterparty must submit coordinates via /receive
C
DOCUMENT-ONLY
No SWIFT connectivity needed

The SBLC is delivered as a certified document package — not a live MT760 transmission. No receiving bank account required. The counterparty receives the instrument via this secure portal or encrypted email. Used when the instrument doesn't need to be “on SWIFT” for monetization (e.g., performance bond, collateral pledge, or custody proof).

✓ No bank account required — portal/email delivery only
Delivery Decision Flow
Case Created
Beneficiary Profile Assigned (legal name, address)
Receiving bank profile provided?
YES → Final delivery sheet → MT799 pre-advice → MT760 transmitted [Option A]
NO → Draft sheet issued (coordinates pending)
↓ Counterparty visits sblc.optkas.org/receive
↓ Submits: bank BIC + account + entity name
↓ Ops verifies → assigns receiving bank profile
↓ Case → FINAL → MT799 → MT760 [Option B]
DOC-ONLY → Document package via portal + email [Option C]
🏦

Counterparty — Receiving an SBLC?

If you were told an SBLC is being arranged for delivery to you, submit your receiving bank coordinates here. You need: your bank's SWIFT BIC, account number, and legal entity name. If your bank isn't SWIFT-connected, select document-only delivery.

Submit Receiving Coordinates
📄

Have an SBLC to Bring In?

Register an existing SBLC or Bank Guarantee for verification and funding review. You can submit immediately even if receiving coordinates aren't confirmed yet — the system issues a draft delivery sheet and waits for final coordinates.

Submit SBLC for Intake
Do You Need Issuer Numbers?

What "Issuer Numbers" Mean Here

The system does not issue reference numbers to the SBLC-issuing bank. Instead, it needs the following from the issuing bank's end:

  • SWIFT BIC — 8–11 character bank code (e.g., HSBCGB2L)
  • MT760 Transaction Ref — Field :20: in the SWIFT message
  • Bank's internal LC/SBLC reference — Field :21:
  • Advising bank BIC — If applicable, field :57A:

What OPTKAS Generates

  • CASE-YYYYMMDD-XXXX — Unique case reference number
  • Facility ID — Assigned after approval & structuring
  • Draw Request IDs — Per disbursement request
  • Settlement TX Hash — On-chain transaction reference
The issuing bank must be pre-approved in the OPTKAS issuer policy registry (by SWIFT BIC) before a case can proceed to funding.
Required to Submit
  • Issuing bank legal name + SWIFT BIC
  • Face value and currency (e.g., USD 10,000,000)
  • Expiry date (minimum 30+ days from today)
  • Applicant legal entity name
  • Beneficiary legal entity name
  • Transferability status (yes/no)
  • Raw MT760 SWIFT text (or structured fields)
Also Required (Before Funding)
  • Applicant & beneficiary KYC/KYB documents
  • Source and use of funds narrative
  • Beneficial ownership information
  • Any side letters or fee letters
  • Governing ruleset (ISP98, UCP600, URDG758)
  • Draw conditions summary
  • Advising / confirming bank details if claimed
🏛

New to OPTKAS?

Take the full platform walkthrough — 18 steps, live API calls, and voice narration covering every aspect of the SBLC lifecycle: intake, policy, SWIFT parsing, risk scoring, committee approval, custody, facility structuring, and on-chain settlement.

▷ Start System Walkthrough
Begin SBLC Intake