Meridian Pay cleared a fintech security review without exporting a single row

Meridian Pay cleared a fintech security review in two weeks by running analytics inside their own warehouse.

Fintech
Industry
9 data, 60 engineering
Team
0 rows exported
Headline result
01

The challenge

Meridian Pay processes card transactions across the EU and UK. Every analytics vendor they evaluated failed the same question: does customer data leave our environment?

Three procurement cycles had already died on data residency.

02

What Trace found

Trace deployed warehouse-native. The analysis compiles to SQL and executes inside their own GlacierDW — the result set returns, the rows never move.

Their row-level security, masking policies and role grants applied unchanged, because Trace is a query rather than a pipeline.

03

Results

Security sign-off took two weeks instead of two quarters. Not one row of transaction data left their environment, and their existing masking policies applied without modification.

  • SOC 2 and GDPR review passed with zero exceptions
  • Row-level security and masking honoured unchanged
  • Sub-two-second answers on billion-row tables
0 rows exported
rows left the warehouse
2 weeks
security review, start to sign-off
<2s
query response on billions of rows

Want to know why your numbers moved?

Calendar

A guided first look, in 30 minutes

Help

Questions before you book?