Skip to content
Glossary

What is Query cache?

Technology

A cache temporarily stores an external source's response to reuse it in later queries about the same applicant, instead of requesting it again. It cuts the cost per bureau query and the flow's response time.

Why it matters

Every bureau or data provider query is paid for. If an applicant retries, if the flow queries the same source in two branches, or if a campaign re-scores a portfolio, without a cache you pay several times for the same data.

The other effect is latency: a cached response does not depend on provider availability, so the flow holds up even when the source is slow.

  • Lower cost on repeated queries to the same source.
  • Faster responses and less dependency on the provider.
  • Requires defining how long a data point stays valid.
FAQ

Common questions

How long should bureau data be cached?+

It depends on how fast it changes and on the risk policy. Identity data tolerates long windows; a score or an outstanding debt loses validity quickly. The practical rule is that savings should never justify deciding on information that no longer represents the applicant.

Can a query bypass the cache?+

Yes. When the decision needs the freshest possible data, the flow can request a live query and ignore what is cached.

Want to see it in your operation?

Transform your credit assessment process with the decision engine.