Outside the bank
Credora's analysis does not stop at the bank's own books. Python UDFs running inside Sapphire Bank's Exasol call three external parties over the public internet, through the HTTPS relays below: 16 UDF instances in parallel, using bulk endpoints, within one RUN_ANALYSIS call. Exasol stages the replies with a purge time and deletes them on schedule, keeping a SHA-256 fingerprint as proof. All three are mocks built for this demo: they imitate the real services and hold only synthetic data.
X-API-Key header. Without it, data calls are refused.
Reading live counts…
Consumer reports for every partner and commercial reports for every company: scores, open facilities, overdues and enquiries.
GST registrations and 2 to 10 years of monthly returns per company: the turnover trail the bank cannot see in its own ledger.
With the partners' consent, their accounts at other banks with transactions: cash flows that never pass through Sapphire Bank.
Every company, partner, PAN, GSTIN, account and score here is generated. These are mocks of CIBIL, GSTN and an Account Aggregator, not the real organisations, and they carry none of their data or branding.
/docs and /health are open to anyone. Every data endpoint requires the X-API-Key header; the key is set per deployment and held by Sapphire Bank's Exasol, so a call without it gets 401.
The other end of these calls is Credora, Sapphire Bank's pre-approved corporate loan app, built on Exasol Personal for ExaThon India 2026. Inside the bank, only the Exasol roles granted it may read the raw replies: loan operations sees the derived features and decisions, relationship managers the decisions; neither reads the raw bureau, GST or Account Aggregator data.