HiPay Group

At a glance

• New merchant back office, which became HiPay Console: the platform's only back office, about 5,000 merchants
• Payment flows: 3-D Secure 2.x, tokenization, retry logic and soft declines, PCI-DSS compliance
• API Platform back end fully replacing the legacy one, React/Material-UI front end
• Faster QA: per-branch Docker test images and automated Selenium tests

Online payment provider listed on Euronext Paris, omnichannel services for merchants across Europe: €2.8bn of transactions processed in 2018, €3.9bn in 2019.

Context

“Console” team: 4 PHP/Symfony/React developers, 1 product owner and 1 QA engineer.

Starting point: a merchant back office resting on an ageing Symfony back end, while processed volumes were growing by more than 30% a year.

Goal: fully replace it with a modern, decoupled application (API + React front end), without interrupting service to merchants and within PCI-DSS constraints.

Stack: PHP/Symfony back end with API Platform, React and Material-UI front end, PostgreSQL, ElasticSearch, RabbitMQ, JWT authentication, Docker, Selenium tests.

Achievements

• New merchant back office: detailed interactive transaction view, filtering, fraud monitoring, summary KPIs and consumer information
• Payment flows: handling of 3-D Secure 2.x authentication, payment-method tokenization, retry logic and soft declines, within PCI-DSS constraints
• API Platform back end designed for robust data handling, fully replacing the previous back end; transaction search and filtering on ElasticSearch
• React front end with Material-UI for an intuitive, responsive interface
• Legacy support: maintenance of the old Symfony system, incident analysis and support
• Delivery tooling: built and maintained CI/CD pipelines, Docker images for test branches, QA datasets, Selenium test automation
• Code review, merge-request validation and pair programming with junior developers

Results

• Back office launched in 2021 as HiPay Console: it replaced the old one and is still HiPay’s only back office today, for about 5,000 merchants (2024)
• Transactions that merchants can browse and filter in detail, with fraud monitoring built into the back office
• Legacy back end replaced by an API Platform API, transaction search on ElasticSearch
• Faster QA thanks to per-branch Docker environments and automated tests