ODG-PASS
Enter app
Fluid Banking · ISO 20022 navigator

Know your payment's fate
before the money moves.

ODG-PASS is a technological navigator, not a bank. It pre-validates ISO 20022 / CBPR+ payment structure (pain→pacs) so your bank sees fewer returns for bad structure — no funds are ever touched; execution and settlement stay with your bank only.

Client pain.001 to optional ODG Gateway to bank path to pacs.008 network — bank executes
Not a second SWIFT · not an ABS replacement · not an Alliance replacement · bank executes
Pre-validation — live Auditor (invoice helper) — live Regulatory sandbox — roadmap
Built on official standards: ISO 20022SWIFT CBPR+pain.001 → pacs.008ISO 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 payment structure ready for your bank to accept, with fewer returns for bad structure. 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).

🛡️

Demo watchlist (advisory)

Demo signal only — not a block, not OFAC/UN/EU screening. Visually separate from structure lights (green/amber/red). Your bank always runs full AML/CFT / sanctions.

💸

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

A keyword / library heuristic proposes the Purpose Code from your free-text description (the old field-70 habit); the officer or client confirms. Final XML / pain.001 is deterministic code, not a model guess.

You write (Ustrd)
"Payment for consulting services, Q2 contract"
Heuristic proposes · you confirm
Purp · SERV — Services
XML: <Ustrd></Ustrd> · <Purp><Cd>SERV</Cd></Purp>

Codes are validated against the full open ISO 20022 ExternalPurposeCode list embedded in the core — no keys, no fees. Human-in-the-loop: the heuristic / library proposes, officer or client always confirms. Final XML / pain.001 = deterministic code, not model guesswork.

Two modes

Optional gateway / navigator · 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

Bank note: client terminal + officer console → structured payments pass cleaner. Gateway optional.

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.

Auditor (invoice helper) · dialogue

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. Invoice-reading helper only — never the authority for compliance or payment decisions.

Modules

What's inside

Each capability with its current status — live now, in testing, or on the roadmap.

Pre-Flight pre-validationRoute, IBAN/BIC, structured CBPR+ address, codes
LIVE
pacs.008 buildISO 20022 pacs.008.001.08 generation
LIVE
Auditor (invoice helper)Helper only · never compliance authority
LIVE
Smart Remittance MappingFree-text → ISO 20022 Purpose Code
LIVE
Demo watchlistAdvisory only · not OFAC/UN/EU · bank runs full AML
DEMO
Bank connection (Mode 2)Bank's own keys — not stored, not seen
BANK KEYS
GCC e-invoicingUBL 2.1 + TLV QR · Oman / Saudi
BETA
Sovereign data nodesIn-country information layer
PLANNED
Roadmap

From a validator to a structured finance navigator

Stage 1 · Technical

Independent validator

Standalone terminal that cleans data flows — pre-validation, pacs.008, AI Auditor. Live now.

Stage 2 · Regulatory

Regulatory sandbox

Enter a regulatory sandbox to legitimise the standard and the sovereign-node model.

Stage 3 · Licensed

Structured reporting hub

With regulator agreements, integrate tax and payment reporting under proper licences.

Contact

Testing with us?

Questions, issues or suggestions — we adjust as we go. Testing phase: no pricing here, tariffs are agreed separately.