# Improving Deployment Success in Payments

> TechSupport Team supported the Terraform and Kubernetes deployment pipeline of FluxPay’s payments platform. Over five months, the client’s GitHub Actions records show successful deployments rising from 74% to 97%.

- Publisher: TechSupport Team
- Canonical page: https://techsupport-team.com/case-studies/payments-deployment-pipeline-reliability/
- Updated: 2026-11-16

Client: FluxPay · Fintech & Payments · UK payments orchestration platform

## Client and engagement facts

- **Client:** FluxPay
- **Industry:** Fintech & Payments
- **Business context:** UK payments orchestration platform
- **Delivery model:** DevOps support
- **Application:** Payments orchestration with per-service deploys
- **Supplied geography:** UK

## Application stack and tools

### Application stack

- Go
- EKS
- Terraform
- PostgreSQL

### Tools used

- GitHub Actions
- Argo CD
- Datadog

Related services: [DevOps support](https://techsupport-team.com/services/devops-support/)

## Why Support Was Needed

The platform deployed about 20 times a week. Production state locks were hard to see in CI logs, and configuration varied between environments. The client’s engineering manager kept production approval.

## Technical Work

- Migrated the whole pipeline to GitHub Actions with per-environment state.
- Introduced a deploy checklist with rollback steps for each service.
- Added a state-lock detector to the deploy logs.

## Representative Incident

After the migration, the first deployment still hit a Terraform state lock from a local apply. On the next attempt, the new detector surfaced the lock and blocked deployment until it was cleared.

## Results and how they were measured

Table: Reported results and their measurement scope

| Metric | Baseline | Result | Units | Measurement window | Source and scope |
| --- | --- | --- | --- | --- | --- |
| Deploy success | 74% | 97% | % | 5 months | Client GitHub Actions; Scope: The five-month comparison excludes a deployment failure during a cloud-provider failover. |
| Rollbacks/week | 5.8 | 1.1 |  | 5 months | Client ArgoCD |
| MTTR | 41 min | 11 min | min | 5 months | Client Datadog |

## Evidence and Limitations

The five-month comparison excludes a deployment failure during a cloud-provider failover. ArgoCD and Datadog supplied rollback and recovery measures.

## Production Deployment Approval

TechSupport Team prepared and tested the pipeline. FluxPay’s engineering manager approved each production deployment.

## Scope a Similar Engagement

Send a recent pipeline failure and identify how your environments, state and deployment approvals are managed. [Request a support plan](https://techsupport-team.com/contact/) or explore [DevOps support](https://techsupport-team.com/services/devops-support/).

## Related pages

- [DevOps support](https://techsupport-team.com/services/devops-support/): The related service for this engagement.

## Contact

Request engineers from TechSupport Team or ask a question: https://techsupport-team.com/contact/
