ODG-PASS is a technological navigator, not a bank. It pre-validates ISO 20022 payments and GCC e-invoices, so you avoid blocks, returns and bank repair fees — and no funds are ever touched.
Built on official standards:ISO 20022SWIFT CBPR+UBL 2.1ISO 13616 · IBANISO 4217 · 3166
Philosophy · Fluid Banking
A navigator between you and the financial protocols
We remove the friction between business and banking standards — making cross-border payments predictable, transparent and error-free. ODG-PASS is an infrastructural adapter, not a financial institution.
🧭
Navigator, not a bank
We don't accept, hold or move funds, and we don't access bank accounts. Money stays inside commercial banks; we work the information layer.
⚡
Predictable
Know the outcome of a payment before it leaves the account — no surprises, no guesswork.
🔬
A sanitary filter for data
Clean, structured, standard-compliant messages out — malformed, ambiguous data caught in.
Pre-Flight Check · Oracle of Transactions
A report on the payment's fate — before money leaves
The core engine inspects each payment up front, so you avoid blocks, returns and the costly repair fees banks charge for malformed MX messages.
🛰️
Route & format
Analyses the route and catches MT/MX format errors, IBAN/BIC issues and unstructured addresses (the CBPR+ killers).
🛡️
Sanctions & blacklists
Names and countries screened before the payment is sent — clear or flagged, you see it first.
💸
No repair fees
Stop rejects and returns at the source. Every result is stamped funds_moved: false.
Smart Remittance Mapping
Type the purpose in plain words — get the right ISO 20022 code
The AI engine reads your free-text description (the old field-70 habit), proposes the correct Purpose Code, you confirm, and the XML keeps both your words and the structured code.
Codes are validated against the full open ISO 20022 ExternalPurposeCode list embedded in the core — no keys, no fees. Human-in-the-loop: the AI proposes, you always confirm.
Two modes
One gateway, two ways to run it
Mode 1 · Automatic
On-site requisite validation
Validate payment requisites right on the site — runs automatically, no login and no keys.
Live now
Mode 2 · Bank connection
The bank connects its own keys — the robot activates
A bank plugs in its own API keys; testing runs inside the bank's own sandbox. ODG-PASS does not store, see or use the keys. No funds move — testing only.
Keys never stored · never seen · no funds
Sovereign Node Architecture
Data stays in its jurisdiction. Money stays in the banks.
We run on distributed sovereign nodes. Only the information layer (invoices, transaction metadata, pre-validation) is localised inside the country; money movement stays entirely within commercial banks and correspondent relations.
🗺️
In-country information layer
Invoices and metadata are processed on a node inside the jurisdiction (e.g. Oman, Saudi Arabia).
🏦
Money stays with banks
We never touch the funds flow — it remains in the commercial-bank circuit.
🚫
No unauthorised export
Cross-border export of metadata is blocked by design — targeting full alignment with GCC and local regulators.
Target architecture for Stage 2–3; the compliance posture is validated step by step with regulators.
AI Auditor · Dialogue Architecture
A guide, not a barrier
The Auditor is proactive — instead of a dry rejection it says "I see an issue, here's option A or B." It takes text, files and voice, cites only official sources, and escalates to a human expert for non-standard cases.