About the client
The client runs a split-payments platform integrated directly with acquirers. Merchants use it to take payments split across several cards, shared among a group, through payment links or in instalments. The platform operates under PCI-DSS, ISO 27001 and GDPR obligations. As transaction volumes and workflow complexity grew, the client engaged FiftyFive Technologies to modernise the platform, migrate core systems and put compliance-driven infrastructure in place on AWS.
Modernising live payment flows without loosening compliance
- Fragmented payment paths. Multi-card, group, link and instalment payments each had their own logic, settlement behaviour and failure modes.
- Limited diagnostics. Constrained real-time analytics slowed detection of pipeline issues and lengthened incident resolution.
- Bespoke provider work. Every new acquirer or gateway needed custom integration, so effort grew with each partner.
- Split codebases. Frontend and backend had to be consolidated into one repository without disrupting live traffic.
- Compliance by design. Infrastructure had to auto-scale while access control, tokenisation, encryption and audit logging were built in rather than retrofitted.
What FiftyFive built
FiftyFive engineered and delivered the modernised platform; the client continues to operate it. The scope covered a modular payment orchestration layer with a single API, real-time analytics and diagnostics inside the transaction pipelines, reusable acquirer and gateway connectors, a monorepo migration with CI/CD, auto-scaling containerised AWS infrastructure with IAM-based access, platform-level tokenisation, encryption and audit logging, A/B testing of user flows, and cross-platform consistency across web and mobile.
How the solution works
One orchestration API
- Workflow-specific integration paths were replaced by a modular orchestration layer.
- Every split-payment type — multi-card, group, link and instalment — runs through the same API surface, so merchants and the client's engineers integrate once.
Observability in the pipeline
- Real-time analytics, monitoring and diagnostics sit inside the transaction pipelines rather than in a separate reporting step, so issues in live payment flows surface as they happen.
Reusable connectors
- A plug-and-play connector model covers multiple acquirers and gateways.
- Adding a provider means configuring a connector rather than writing a new bespoke integration.
Delivery pipeline and infrastructure
- Frontend and backend live in one monorepo with CI/CD pipelines that automate build and release.
- Services run in containers on auto-scaling AWS infrastructure, with AWS IAM governing infrastructure permissions.
Compliance controls
- Sensitive payment data is tokenised, encryption is enforced across the platform and audit logging provides traceability and compliance evidence, supporting the client's PCI-DSS, ISO 27001 and GDPR obligations during the modernisation.
Technology stack
What the solution enabled
Business transformation
Less integration effort
Faster incident resolution
Shorter release cycles
40% less integration effort
For the client's engineering team, through the single orchestration API.
35% faster incident resolution
Through real-time analytics in the transaction pipelines.
New acquirer integrations in days, not weeks
Through reusable connectors.
25% shorter release cycles
After the monorepo migration and CI/CD.
FiftyFive Technologies modernised the platform of a fintech company that lets merchants split payments across multiple cards, groups, payment links and instalments. FiftyFive rebuilt the payment orchestration layer behind one unified API, embedded real-time analytics and diagnostics in the transaction pipelines, replaced bespoke acquirer integrations with reusable connectors, migrated frontend and backend into a monorepo with CI/CD, and deployed on auto-scaling AWS infrastructure. Integration effort fell by 40%, incident resolution became 35% faster, release cycles shortened by 25% and new acquirer integrations went from weeks to days.
Technical questions
How do you add payment providers without bespoke integration work each time?
FiftyFive Technologies replaced provider-specific integrations on this split-payments platform with a plug-and-play connector model covering multiple acquirers and gateways, behind a single payment orchestration API. Adding a provider became a connector task rather than a new integration project, and new acquirer integrations went from weeks to days.
How do issues in live payment flows surface as they happen?
Real-time analytics, monitoring and diagnostics sit inside the transaction pipelines rather than in a separate reporting step, so issues in live payment flows surface as they happen.