ODG-PASS Gateway — structured payment data before sending. Signal, not a verdict. Submission 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. When the bank and its clients use the terminal, each payment is fully transparent: structured fields, purpose code, and 🟢🟡🔴 guidance — visible before submission. 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 · structured payment data · ISO 20022
Correct structured data before you send to your bank.
The terminal checks ISO 20022 structure, common rejection reasons, and field guidance — we show which field to fix. And when e-banking cannot yet carry payments under the new rules, by agreement with your bank you can use this terminal as a structured channel for the transition period. Submission and execution stay with your 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 nowField-by-field guidance · 🟢🟡🔴Guidance only — not a bank verdict
ODG-PASS helps you see structure problems early and prepare fields — before sending. It does not replace your bank's compliance department or execute payments.
Explains which field to fix — 🟢🟡🔴 with clear field guidance
Correspondent guidance — large amounts, cross-border, documents
Shows a demo sanctions signal for manual review — not a block
By bank agreement, acts as a transition channel when e-banking cannot yet carry the new format
What it does not do
Full OFAC / UN / EU screening or bank AML/CFT
Does not execute payments or access your account
Legal approval or guarantee the bank will accept the payment
KYC, PEP, beneficial-owner checks, or regulatory filings
Replace e-banking without your bank’s agreement
Yellow flags are advisory — prepare invoice or contract if asked. Red means fix structured data before sending. The bank always has the final say.
Built on official standards:ISO 20022SWIFT CBPR+UBL 2.1ISO 13616 · IBANISO 4217 · 3166
Who are you?
Product: payment terminal · related tools
Main product — payment terminal (structure check, 🟢🟡🔴, pain/pacs). Bank pack and GCC tax are related paths, not the same claim.
Product · Terminal
I send payments
Check structure before you send — fields, purpose code, correspondent hints (🟢🟡🔴). By agreement with your bank, if e-banking cannot yet handle the new format, you can also use this terminal as a structured channel during the transition.
While e-banking still uses legacy format — an MT→MX tool for your clients: ISO 20022, pain.001 / pacs.008, full structure. Bank and client share one clear data path — payment transparency at initiation. You decide how to grant access. Implementation pack for IT and compliance.
Supporting help — not the payment check itself. Ask about the terminal, bank connect, MT→MX fields, license keys, and roadmap before you send. Full AML/CFT and execution stay with your bank.
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.
🔬
Transparent for the bank
Output is a complete structured message — nothing truncated, nothing missing. Bank and client see the same clear fields before submission; 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).
🛡️
Watchlist signals (demo)
Advisory flags on a demo reference list — guidance only, not a verdict. 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
Describe the purpose in your payment details — 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 Consultant answers from the ODG-PASS library: Terminal v1, bank connect, license vs sandbox keys, MT→MX field changes, roadmap. Text or voice; official sources; human expert for unusual 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, Consultant — 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.