ODG-PASS ISO 20022
Gateway · Practical Guide
ODG-PASS Gateway — correct structured data. Submission and execution stay with your bank. We never ask for logins or API keys on this site.

How to use ODG-PASS Gateway

A short practical guide. ODG-PASS Gateway forms and checks structured ISO 20022 payment data before it reaches the bank. You see 🟢 🟡 or 🔴 with a clear note on which field to fix. You can also — by agreement with your bank — use the terminal as a structured channel during the MT→MX transition when e-banking cannot yet carry the new rules. You always submit through your bank.

BusinessBank staffGCC tax

1Start from the homepage — two paths

On the main page pick a path: the client terminal or the bank gateway. GCC tax is an adjacent module, not the payment terminal.

You send paymentsClient terminal
BankGateway in the bank contour
GCC taxAdjacent e-invoice module

2Payment pre-check (terminal)

Open the validator from the homepage or the button below. Also useful: MT → MX side-by-side guide — the same demo payment in old and new format.

  1. Click one of the sample payments (correct and with errors) — fields fill and the check runs. Or enter requisites manually.
  2. Press Check & build. The terminal checks structure: IBAN/BIC, address by field, purpose code, and other required elements.
  3. Read the traffic light: 🟢 data correct · 🟡 review · 🔴 fix the field — with a clear explanation. Bank view adds technical detail below.

3Transition channel — with your bank

The terminal is not only a pre-check. During the move to ISO 20022, many e-banking screens still cannot carry payments under the new rules.

  1. Businesses: by agreement with your bank, you may prepare (and, where the bank enables it, submit via the agreed path) structured payments through this terminal for the transition period.
  2. Banks: when you and your clients use the terminal, each payment becomes fully transparent — structured fields, purpose code, and 🟢🟡🔴 guidance visible before submission.
  3. Access and how ready MX enters the bank’s systems remain the bank’s decision. ODG-PASS forms correct structured data; execution stays at the bank.

4Consultant

Not sure? Ask about the terminal, bank connect, MT→MX, license, or roadmap.

  1. Type, speak, or attach a PDF / image.
  2. Answers cite official sources only.
  3. Unusual cases go to a human expert.

5Smart Mapping (Purpose Code)

Describe the payment in everyday words — get the correct ISO 20022 Purpose Code. You always confirm.

  1. Write e.g. “rent for July” or upload a text PDF invoice.
  2. Pick the proposed code or choose from the full list.
  3. Copy the XML snippet for your pain.001 — Ustrd + Purp. The bank forms pacs.008.

6GCC e-invoicingBETA

From the GCC tax module: invoice PDF → UBL 2.1 + QR. Format check only — not official filing on our behalf.

  1. Pick country (KSA / UAE / Oman) and invoice type.
  2. Confirm seller, VAT/TRN, line items — you always review.
  3. Download UBL XML. BETA notice on every page.

7For banks — gatewayWORKS

The gateway operates inside the bank contour: structure customer intake into pain.001.001.09, verify CIF and purpose activity matching, and emit compliant pacs.008 and pacs.009 COV to SWIFT Alliance. Clients prepare structured pain.001; execution and debit stay at the bank.

  1. Today: use the public terminal to check structure and download pain.001 — no bank keys on this site.
  2. Banks: open For banks for the gateway, operations workplace, and implementation pack.
  3. The check covers data only — signal 🟢🟡🔴 is guidance, not a verdict. Submission and execution stay with your bank.
Check payment → Desktop → Support → For banks →
ODG-PASS forms correct structured payment data — from the client to the bank. Scope: structure and correctness before sending. Traffic-light results are guidance. You always submit through your bank.