All customer stories

How one of the largest banks in APAC built a single access layer for external data and services

AccessWay now sits between the bank's channels and applications and the external data ecosystem: credit bureaus, government and public infrastructure APIs, and specialist data vendors. Every team uses one API, one set of contracts, and one view of cost.

Challenge

As the bank grew its digital channels, each application team went out on its own to source the external data it needed. Loan origination connected to credit bureaus and GST. Onboarding connected to eKYC and DigiLocker. Cards, wealth and collections each built their own links to the same providers.

1,000sof point-to-point integrations

Every application built its own connection to every external data and service API it needed. Each one had to be secured, monitored and maintained on its own.

0single source of truth for contracts

Each business unit negotiated with vendors separately. The same provider was contracted several times, on different terms and at different prices.

2–3×repeat fetches of the same data

Nothing was shared or cached across bank assets. The same customer record was fetched, and paid for, again by each team that needed it.

The result was an integration estate that grew with every new app and every new provider. Adding a vendor meant months of work across many teams. Switching one meant re-integrating every application that used it. Nobody could answer a simple question: how much is the bank spending on external data, and on what?

80 integrations from a sample of 8 applications and 10 providers. Across the whole bank, this ran into the thousands.

Solution

The bank deployed AccessWay as a single access layer for all external data and services. Applications now integrate once, with one standard API. AccessWay handles provider connections, contracts, routing, failover and caching behind it.

  1. Integrations
    N × NN × 1

    Each channel and application connects to AccessWay once. AccessWay handles every external provider behind one standard contract.

  2. Vendor onboarding
    Per appOnce

    Vendors are selected, priced and onboarded centrally, then shared across every business unit, channel and application.

  3. Switching cost
    HighZero

    Applications call a vendor-neutral API, so the bank can change or add a provider without touching a single application.

  4. Continuity
    Vendor-ledBank-led

    Failover across providers keeps journeys running when one vendor is down, on top of each vendor's own availability.

  5. New requirements
    Per teamOne door

    One point of contact. AccessWay onboards a new provider once and every application can use it the same day.

Results

Lower cost for every call

With contracts and traffic consolidated, the bank negotiates as one buyer. Shared caching cuts paid calls further, because data already fetched for one journey can be reused by another.

  • Credit bureau
  • PAN verification
  • GST returns
  • Bank statements
  • Vehicle registry
Illustrative view. Every call is tracked by API, provider and cost.
Volume discounts

One bank-wide contract per provider replaced many small ones. Pooled volumes moved the bank into better pricing tiers.

Savings from caching

Data fetched once is reused across channels and applications within its validity window, so the bank pays for it once.

Full cost transparency

Usage and billing dashboards show who called which provider, how often, and what it cost, down to the business unit.

Control and auditability

Admin UIs, business consoles and built-in reports let teams manage access, set limits and produce an audit trail on demand.

New providers in days, not months

With our smart blueprinting and AI-led development of provider plugins, the time to new provider onboarding has also drastically reduced, giving applications availability to newly launched data and services within days, not months.

Want one access layer for your bank?