Publish once. Reach every treasurer.
Product managers maintain capability records in the GlazBox publishing workspace. Every change is versioned, approved by a checker, and released to subscribers the moment it goes live.
Financial institutions maintain their capabilities through maker-checker workflows. Subscribers see only approved versions — always current, always comparable.
Product managers maintain capability records in the GlazBox publishing workspace. Every change is versioned, approved by a checker, and released to subscribers the moment it goes live.
Every family follows the same governed structure — so a Yes means the same thing at every institution.
Payment products including telegraphic transfers, ACH, RTGS and instant payments — with rails, cut-offs and FX options per currency and market.
Collection products including receivables collection, direct debits and cheque collection — instruments and channels per market.
Account opening and maintenance, statements and virtual accounts — the account backbone under every capability.
Trade products including letters of credit, guarantees and documentary collections — as modelled by the platform today.
Guaranteed and market rates, portal and voice booking, auto-FX thresholds and currency-pair coverage — attached to each payment and collection product, and modelled as a family in its own right.
The sourcing workflow runs on the data already published. Financial institutions respond in their own workspace, under the same maker-checker controls that govern publishing.
Institution-owned, approved dataFinancial institutions publish and manage their own capability records.
Version history & provenanceWho published what, when, and who approved — a full audit trail on every record.
Neutral comparisonSide-by-side, differences highlighted — nothing ranked, nothing scored.
One dataset across the lifecyclePublishing, comparison and sourcing all run on the same governed registry.