ODG-PASS — clean ISO 20022 structure before the bank (pain.001 from the client; the bank forms pacs.008) · confirm arrival with pain.002. Public demo free · unlock for the working terminal · Download the Windows client. Execution stays at your bank.
For banks
Fewer returns. Clean ISO 20022 in and out.
The console sits in the bank’s contour. It translates MT ↔ ISO 20022 both ways and shows the officer what will stop the payment. Core banking is unchanged. Clients prepare pain.001; the bank’s server forms pacs.008.
Flow-copy pilot: a copy of outbound messages — no change to the payment path
Client terminal: pain.001 as a file or on issued keys; the bank forms pacs.008
Security appendix + cover letter (EN / AR) for IT and the supervisor
ODG-PASS · clean cross-border payments · ISO 20022
Make the payment clean before it reaches your bank.
The terminal builds a clean ISO 20022 pain.001 instruction — a file for e-banking upload, or a connected send on keys your bank issued. The bank’s server forms pacs.008 after it books the debit. Confirm arrival with pain.002. Browse the public demo freely; unlock a test key for the working terminal; or download the Windows client — the installer is the same for everyone, the access key is issued separately. Your bank executes.
Returned with no clear reason? Usually the message was not structured for the new standard. Fix that before the bank — then confirm it arrived.
Public demo · no keyWorking terminal after unlockWindows client · open download
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?
Enter as client · connect as bank
One product, two doors: enter as client (browser terminal or Windows download) or connect as bank (implementation pack). GCC tax is a related path.
Client
I send payments
Send clean the first time — know that the full amount arrived. Start with the public demo, unlock a client test key for the working terminal, or download the Windows client. The installer is open; the access key is issued separately.
Console in the bank contour: MT ↔ ISO both ways, officer queue, fewer returns. Clients prepare pain.001; the bank forms pacs.008. Open the bank page or unlock with a bank test key.
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.
Data layer · client to bank
Data layer between client and bank
ODG-PASS forms a clean ISO 20022 pain.001 for how you connect to your bank. The bank’s server forms pacs.008. Our scope: clean message + structure. 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 · structure before sending
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.
Sign in with a client test key for the working terminal, or download the Windows client. The installer is the same for everyone; your personal key is issued separately.
Test key · live terminal · Windows client download
Fewer returns. MT ↔ ISO translation both ways. Officer workplace plus a client terminal that prepares pain.001. The bank forms pacs.008. Implementation pack for IT — no public API keys on this site.
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 — later stages, not required for today's payment check.
Stage 1 · Technical
Independent validator
Pre-validation, pain.001, Consultant — works now.
Stage 2 · Regulatory
Regulatory sandbox
Legitimise the standard with regulators.
Contact
Testing with us?
Questions or issues — use Support, or contact us below. Testing phase: no pricing here; tariffs are agreed separately.