Core banking
SWIFT gateway
The SWIFT gateway is the most tangible "this is real software" moment on the platform. You give it an IBAN and it makes a live call to a public bank directory, returns the real bank behind that account, and decodes the BIC to its country and location — the first step of any cross-border payment.
What actually happens
The gateway validates the IBAN with the ISO 13616 mod-97 checksum, then calls the public openiban.com directory — no API key, no mock — to resolve the bank and its BIC. It then decodes the BIC under ISO 9362 into bank, country, location and branch. If the network call fails, it falls back to a local decode so the screen never breaks, and it tells you which path it used.
Where the honesty line sits
Resolving a bank from a directory is live. Actually tracking a payment across the SWIFT network — gpi status, confirmations — needs SWIFT membership and a signed connection, which a proof-of-concept cannot have. The platform does the real part it can, and is explicit about the part it cannot.
Good to know
Try a real IBAN from your own bank — the resolved name and BIC are coming back from a live directory, not a lookup table.
The developer & connectivity page shows the exact public request, so you can run it yourself in a terminal.