The client terminal structures payment instructions from 1C, Balance BDO, or invoices into clean pain.001.001.09 with an Accountant Ledger Room and printable bank receipts (pain.002). The bank gateway operates inside the bank’s contour on the officer desk, verifies CIF & correspondent routes, and emits compliant pacs.008 to SWIFT CBPR+ and NBG Montran ATS without changing the core banking system.
Explore all dedicated tools and modules designed for corporate payers, bank operations centers, and compliance officers.
Structures corporate payment instructions before they reach the bank. Parses unstructured lines into mandatory postal fields (country, town, street, building, post code) to comply with SWIFT 14 Nov 2026 mandate. Assigns 4-letter ISO purpose codes, generates traffic lights 🟢🟡🔴, and exports clean pain.001.001.09 XML.
Open Terminal →Built for Georgian companies and banks (NBG Montran RTGS ISO 20022, TBC Bank BIS v1 / SOAP, Bank of Georgia XS2A). Features clean Accountant Mode (no raw XML tags), 1C / Balance BDO import, RS.ge State Treasury 9-digit budget codes, printable bank receipt (pain.002) with stamp, and a dedicated Payment & Fee Journal Room.
Operates inside the bank’s own contour on top of existing core banking systems (BSC Gemini G6, Temenos, Flexcube). Harmonises BIS CPMI Report 230 Graph 1, NBG Montran RTGS ISO 20022, TBC BIS v1 / SOAP, BOG XS2A, and emits verified pacs.008 / pacs.009 COV to SWIFT Alliance with 4-Ledger Officer Reconciliation.
Bank Architecture & Parameters →Interactive 3D intelligence assistant backed by Google Gemini 3.8 and an official library of BIS CPMI, SWIFT CBPR+, NBG Montran ATS, and SEPA standards. Explains return reason codes (AC01, BE04, CH16, NARR), checks counterparty activity alignment, and speaks answers aloud.
Open 3D AI Consultant →Interactive architectural and executive consulting studio powered by Google Gemini 3.8. Switch between 5 specialized advisors: Enterprise Bank Architect (BIS d230), ISO 20022 XSD Engineer, Georgia Montran ATS & TBC/BOG Specialist, Executive Pilot Advisor, and Compliance OSINT Analyst.
Open Gemini 3.8 Advisory →Interactive comparative map of legacy SWIFT MT (MT103, MT202, MT950) vs ISO 20022 MX (pacs.008, pacs.009, camt.053). Demonstrates where field truncation happens, why 1-line addresses cause NAK bounces, and how Field 70 is divided into Remittance and Purpose.
Explore Field Guide →Intelligent semantic classifier that translates invoice contract text into strict 4-letter ISO 20022 Purpose codes (GDDS, SCVE, EQUP, INTE, etc.). Verifies counterparty activity matching to ensure correspondent filters do not halt or reject the transaction.
Try Smart Mapping →Dedicated regulatory tax module for Saudi Arabia, Oman, and UAE. Validates and generates UBL 2.1 electronic invoices, checks required tax fields, and computes cryptographic TLV Base64 QR codes compliant with ZATCA (Fawtara Phase 2) and Oman Tax Authority rules.
Open Tax Module →Unified operational workspace and standalone Windows client (ODG-PASS-Terminal-Georgia.exe). Enables corporate accountants and treasury teams to process invoices, 1C / Balance BDO exports, verify IBANs, and maintain a local Payment & Fee Journal Room on their PC.
Download Desktop Client →Library and rules, not a generative model.
From client instruction checking in the terminal to inbound processing and SWIFT release on the bank operations desk — without changing the core accounting system.
MT fields are shorter than matching MX elements. Part of the content gets cut off during conversion. Neither sender nor receiver sees that it was lost.
Data is stored as a continuous line. International networks require street, building, post code, town, and country as discrete fields. A translator cannot invent structured addresses from raw text.
The network and correspondents require a standard ISO Purpose code. MT has no separate field for it: free text in the old style is not a classified code.
A missing status, cover confirmation (pacs.009 COV), or inquiry is often left untracked. Delay is only learned from the frustrated client.
The client terminal puts the payment in order on your side, before it goes to the bank. It turns invoice details into clean, structured ISO 20022 customer instructions — pain.001 and pain.001.001.09. You see every missing field and correct it before sending. Submission and debit stay at your bank; the bank issues pain.002 status and releases pacs.008 to SWIFT.
The gateway is installed in the bank’s own contour. It ingests customer instructions (pain.001 or legacy formats), matches with the bank’s CIF client cards, and presents clean structure to the operations desk. Once the officer confirms the structure, the bank emits pacs.008 and cover pacs.009 COV directly to SWIFT Alliance.
ODG-PASS structures and validates payment data between the client and the bank. Submission, debit, and execution stay with your bank. The operations desk operates inside the bank’s sovereign contour.
Questions or technical inquiries — use Support, or contact our engineering team below. Testing phase: no pricing here; tariffs are agreed individually.
