THE PRODUCTION REALITY GAP

Between everything that clears your checks and what your customer experiences, there is a gap.
It is where your customers actually are.

For over 20 years we have worked with banks, and only banks, on a single problem: everything inside can look correct while a real customer still cannot complete a critical journey. It happens the day something new goes live, and it happens on any ordinary day a service is running. This page explains why that gap exists, why it is structural rather than a failing of any team, and what it takes to close it.

INSIDE THE BANKCUSTOMER’S SIDE
Systems healthyOutcome unknown

Two views. One live payment.

TWO DISCIPLINES

Two disciplines that do their job,
and the space between them

BEFORE PRODUCTION

Testing & quality assurance

Testing and quality assurance verify everything possible before a release reaches production. But they verify it in an environment that, by design, is not production. Pre-production cannot hold real customers, real balances, real counterparties, or the full behaviour of the live systems around them. A residual uncertainty always survives to go-live. This is not a shortcoming of the QA team. It is the boundary of what pre-production can see.

FROM INSIDE PRODUCTION

Monitoring, APM & observability

Once a service is live, your monitoring, APM, and observability platforms turn metrics, logs, and traces into real-time insight into system behaviour, tracing transactions across every dependency, flagging anomalies, and pinpointing root cause to protect your SLOs and reduce mean time to resolution. This is essential, and it is done well. But it observes from the inside. It infers the customer’s experience from system telemetry rather than confirming it directly. A dashboard can show every component healthy while a customer, for reasons that never reach the telemetry, cannot complete a payment.

Between the two sits a view that neither is built to produce: the customer’s own perspective, in live production, captured directly rather than inferred.

A STRUCTURAL GAP

The gap is structural, not a failing

This is not a gap any team created, and it does not close by testing harder or adding another dashboard. Pre-production cannot become production. Inside-out telemetry cannot become the customer’s point of view. The gap is a property of where each discipline stands, not a measure of how well it works. Closing it requires standing somewhere neither of them can: outside the bank, in live production, as the customer.

Pre-productioncannot becomeProduction
Inside-out telemetrycannot becomeThe customer’s point of view

OUTSIDE-IN PRODUCTION VERIFICATION

A third discipline

We call this outside-in production verification. It is not testing, which happens before production. It is not monitoring, which observes from within. It is a distinct discipline that verifies, from the outside in, whether a real customer can complete a real journey in live production, and produces the evidence that it did, or the evidence of exactly where it did not.

01

Testing

Before production

Verify everything possible before a release.

02

Monitoring

From inside production

Understand the health of your systems.

03

WTSS

As the customer

Confirm the real journey and its outcome.

OUR METHOD

Our method: we become the customer

  1. 01

    Real funded accounts

    We hold a global network of over 800 funded, KYC-approved accounts across 26 countries, at real banks.

  2. 02

    Real authentication

    Using proprietary authentication robots, human-to-machine and machine-to-machine, we log in and act exactly as a customer would, across web, app, API, and file.

  3. 03

    Real customer roles

    We run the mission-critical journeys in real roles: initiator and approver, buyer and seller, debtor and creditor.

  4. 04

    Verified outcomes

    We verify what actually happened, black-box, with no inside knowledge. For a payment, that includes confirming the money reached the beneficiary.

  5. 05

    Evidence of every run

    Every run produces evidence: timestamped logs, journey outcomes, and video and screenshots of what the customer saw. Evidence ready for an auditor or a board.

  6. 06

    A certified platform

    All of it runs on our own ISO 27001 and 27701 certified platform, hosted in Tier 4 data centres in the Netherlands at 99.995% availability.

THE INFRASTRUCTURE BEHIND THE METHOD

Why this is difficult to build,
and rare to find

The largest banks have the talent to attempt this. What takes years to build is everything around the talent: the network of funded real accounts across borders, the authentication robots at scale, and the discipline to operate all of it safely in production, continuously, for a bank. We are unique in what we do. For more than 20 years we have been the only company that verifies live customer payment journeys in production as a real customer, trusted to do it daily by some of the largest banks in the world. We have spent over 20 years building it, for banks, and only banks.

Real accounts. Real banks. Across borders.

800+
funded, KYC-approved accounts
26
countries, real banks
20+
years, working only with banks

THE SAME METHOD, TWO NEEDS

Two ways banks put it to work

The same method meets two different needs.

BEFORE A CHANGE

LaunchGuard and ChangeChecker

Before a change reaches customers, we act as the first customer in production and give a clear go or no-go. This complements the testing and quality assurance process. Delivered as LaunchGuard and ChangeChecker.

Explore LaunchGuard + ChangeChecker

WHILE A SERVICE RUNS

TrueSight

While a service runs, we verify the critical journeys continuously and feed the customer’s perspective into the observability stack, with evidence the moment something breaks. This complements monitoring and observability. Delivered as TrueSight.

Explore TrueSight
See what we verify →

INDEPENDENT CUSTOMER-SIDE EVIDENCE

On regulation

For European institutions, this discipline also answers a regulatory need. DORA has applied across the EU since 17 January 2025 and requires financial entities to test operational resilience and to report major ICT-related incidents. Independent, outside-in evidence of whether services hold up in production, and a record of incidents when they do not, is precisely the kind of proof that obligation calls for. For banks outside the EU, the same evidence serves the same purpose for boards and auditors, without the regulatory deadline.

The customer-side record

VIDEOSCREENSHOTSLOGS

One journey. Three forms of proof.

ING / IN PRACTICE

At ING, this is already how a global bank works with us. We continuously verify their critical customer journeys from the outside in and feed that signal into their platform, and when a journey fails we supply the evidence they need to act on it and to account for it, including timestamped video and screenshots of exactly what the customer encountered. That independent, customer-side record supports both faster resolution and DORA reporting.

Timestamped videoScreenshotsCustomer-side record

BANKS, AND ONLY BANKS

Who we are

We are a specialist firm that has worked with banks, and only banks, for over 20 years. Our clients include some of the largest institutions in the world. We are deliberately narrow: we do one thing, we do it in live production, and we do it from the customer’s side.

One thing.
In live production.
From the customer’s side.

Already in production inside
some of the world’s largest banks.

CitibankCrédit Agricole CIBRabobankING

SEE YOUR CUSTOMER’S PERSPECTIVE

See what your customers actually experience.