CUSTOMER STORY
How EPI Company tests secure payment systems at scale
You'll learn:
- How EPI defines SLOs and throughput expectations for payment-critical services
- Why mTLS, HMAC, and JSON Web Key auth flows create hidden CPU overhead inside load tests
- How pre-generating cryptographic keys cut simulation cost and restored runner headroom
- How the team structures governance: private runners, SSO, and infrastructure cost controls
- How GitHub integrations and Gatling Enterprise Cloud support continuous performance validation
- The lesson they'd apply from day one: optimize the simulation before you scale the infrastructure
Speakers
Kyriakos Vallianatos
Backend Software Engineer
EPI Company
Diego Salinas
Content Marketing Manager
Gatling
.avif)
Join this session
Free. Live or on demand: register and we'll send you the recording.
ABOUT THIS SESSION
When your payment infrastructure processes transactions for hundreds of millions of users across Europe, performance testing isn't optional — and getting it wrong isn't a slow day, it's a regulatory incident.
Join us to hear how EPI, the organization behind Wero, approaches load testing inside one of the most security-constrained environments in European fintech.
In this session, Kyriakos Vallianatos will walk through how the team defines SLOs, handles cryptographic authentication flows in their simulations, and resolved a critical CPU bottleneck caused by in-test key generation.
This is a practitioner-first session with real architecture decisions, honest tradeoffs, and lessons that transfer directly to any team running load tests against systems with non-trivial auth requirements.
Your all-in-one load testing platform
Design complex tests, manage global infrastructure, and turn results into action on one powerful platform.
Need technical references and tutorials?
Minimal features, for local use only
