ODG-PASS Gateway
Check payment
ODG-PASS Gateway — корректные структурированные данные платежа. Отправка и исполнение выполняются вашим банком.
For banks & regulators

MT → MX: deploy without rebuilding all of e-banking

A ready implementation pack — run validation inside your perimeter, give clients a channel during migration, and show supervisors a clear security story. Scope: structured payment data — execution stays at the bank.

Open bank implementation pack → MT → MX · video guide → Cover letter · EN + العربية
ODG-PASS Gateway · structured payment data

Correct structured data
from client to bank.

The terminal forms payment data to ISO 20022 requirements — before it reaches your bank. We are responsible for data correctness and structure; execution stays with the bank.

Your payment returned and nobody explained why? Usually the data wasn't structured the way the new standard requires. The terminal shows that before you send.

Payment check — works now Plain-language results · 🟢🟡🔴
Check payment → Bank pack → Choose your path
Built on official standards: ISO 20022SWIFT CBPR+UBL 2.1ISO 13616 · IBANISO 4217 · 3166
Who are you?

Four entry points — one product

Structured payment data from client to bank. Pick your path — clear guidance, traffic-light results 🟢🟡🔴.

Bank staff

I work at a bank

ISO 20022 pre-validation for compliance. Signal, not a verdict. Full implementation pack for IT, compliance & regulators — MT→MX client bridge.

Implementation pack → Cover letter EN+AR Try Mode 1 view
Business

I send payments

The terminal guides you through structured fields, maps your purpose to the right code, and shows 🟢🟡🔴 before you send to the bank.

Check payment →
GCC tax

I need e-invoices

Invoice PDF → UBL 2.1 + QR for ZATCA / Oman / UAE. Demo — format check, not official filing on our behalf.

Tax terminal →
Need help?

Not sure? Ask the AI Auditor

ODG-PASS helps you check payment data before you send — structure only, no payment execution. See if the payment will reach the client and whether hidden block reasons (often not explained by SWIFT, TIT, or the bank) apply.

  • Text, file or voice
  • Official sources only — no guessing
  • Human expert for unusual cases
Open AI Auditor →
How it works

Three steps — check before you send

AI helps read and explain. The final XML is deterministic code — not model guesswork.

①

Fill in or upload

Payment details or invoice PDF — in your browser.

②

We check the standards

ISO 20022 / UBL rules — you see 🟢 🟡 or 🔴 with a clear note on which field to fix.

③

Send via your bank

Fix what's flagged, export structured data, send through your bank. Execution is the bank's job.

Philosophy · Fluid Banking

Data layer between client and bank

ODG-PASS Gateway forms correct structured payment data. Our responsibility: correctness and structure. Sending and execution: your bank.

📋

Structured by design

Address by fields, purpose as a code, mandatory identifiers filled — at the point of entry, not after rejection.

⚡

See before you send

Check the payment, change nothing in the bank — see 🟢🟡🔴 with a clear explanation of which field to fix.

🔬

Ready for the bank

Output is a complete structured message — nothing truncated, nothing missing. The bank's translator has what it needs.

Pre-Flight Check · Oracle of Transactions

Payment data check — before it reaches the bank

We check each payment before it reaches the bank — so you see problems early, not after a rejection.

🛰️

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.

💸

Fewer rejections & repair fees

Wrong structure means rejection and repair fees. The terminal catches it at source — when you fill in the payment, not a week later.

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.

You write (Ustrd)
"Payment for consulting services, Q2 contract"
→
AI 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 AI proposes, you always confirm.

Try Smart Mapping →
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 staff

Deeper check — by invitation only

For bank employees: the validator highlights which fields need attention. No API keys on this public website — bank onboarding is arranged separately. Signal only, not a block.

By invitation · no keys on site
Bank pack · MT→MX →
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.

Open the AI Auditor →
Modules by role

What each client gets

Three simple statuses: Works · Demo · Soon.

Business

  • Payment check · Works
  • Traffic light 🟢🟡🔴 · Works
  • pacs.008 on success · Works
  • Smart purpose mapping · Demo

Bank

  • ISO 20022 pre-validation · Works
  • Sanctions signal (not a block) · Demo
  • Staff validator Mode 2 · Soon
  • No keys on public site · Works

GCC tax

  • UBL 2.1 + QR · Demo
  • ZATCA / Oman / UAE · Demo
  • Yellow-field OCR hints · Demo
  • Official filing via your ASP · Soon
Roadmap & sovereign architecture (for partners)

Target architecture: information layer localised in-country; money stays in banks. Validated step by step with regulators — Stage 2–3, not required for today's payment check.

Stage 1 · Technical

Independent validator

Pre-validation, pacs.008, AI Auditor — works now.

Stage 2 · Regulatory

Regulatory sandbox

Legitimise the standard with regulators.

Stage 3 · Licensed

Financial hub

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.

✈️Telegram+968 79690973 💬WhatsApp+968 79690973 ✉️Email[email protected]