ODG-PASS Gateway — compliance rehearsal and structured payment data before your bank. Signal, not a verdict. Sending and execution stay with your bank.
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.
Step-by-step pilot: Connector, license, sandbox — two keys, not mixed
Client bridge: structured MX (pain.001 / pacs.008) without field truncation
Security appendix + cover letter (EN / AR) for IT and the supervisor
ODG-PASS Gateway · compliance rehearsal · ISO 20022
Rehearse the payment before your bank decides.
The terminal checks ISO 20022 structure, common rejection reasons, and advisory compliance flags — what correspondents often ask about. We prepare data and explain what to fix; your bank runs full AML/CFT and executes the payment.
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 nowPlain-language results · 🟢🟡🔴Rehearsal only — not bank compliance approval
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.
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).
🛡️
Compliance signals (demo)
Advisory flags on a demo reference list — rehearsal only. Your bank runs full sanctions screening and AML/CFT.
💸
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.
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.
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.
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.
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.