ODG-PASS — clean ISO 20022 messages before the bank (pacs.008 / pain.001) · confirm arrival with pain.002. Free demo on the site · real work in ODG-PASS Desktop. Execution stays at your bank.
For banks
Fewer returns · clean ISO 20022 at intake
Connect your channel so clients prepare clean pacs.008 or pain.001 before messages hit your core. Less scrap, clearer structure, transparent fields at initiation. Execution and AML stay 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 · clean cross-border payments · ISO 20022
Make the payment clean before it reaches your bank.
The terminal builds a clean ISO 20022 message — pacs.008 when your bank gives a token, or pain.001 for manual e-banking upload — and helps confirm the full amount arrived (pain.002). Free demo on demo data; real work in ODG-PASS Desktop after registration. 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.
Free demo — on the siteClean pacs.008 / pain.001Desktop — after registration
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 (demo → Desktop) 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. Ask your bank to connect. Try the free demo, then download ODG-PASS Desktop for real work.
Less scrap at intake, fewer returns, clean ISO 20022 from clients. Connect your channel — clients prepare pacs.008 or pain.001 before your core. You decide access.
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 is a hybrid terminal: it builds a clean ISO 20022 message for how you connect to your bank — pacs.008 or pain.001 — and helps confirm arrival. 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 · 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.
Try the free demo on the site. After registration, ODG-PASS Desktop builds clean pacs.008 / pain.001 locally and helps confirm the full amount arrived. Ask your bank to connect for the token path.
Fewer returns and cleaner ISO 20022 at intake. Clients prepare structured messages before your core. Implementation pack for IT and compliance — 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 — 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.