paymentprovider-br-dge
Payment provider adapter API integrating TC's payment platform with the BR-DGE (Comcarde) payment orchestration service for card, Apple Pay/Google Pay and alternative payment methods.
Health score
0 to 100 across seven weighted factors; nothing is hidden. Green is 75 and above, amber 50 to 74, red below 50. How scoring works.
Facts
| Languages | csharp |
| Frameworks | ASP.NET Core 8, MediatR 12, Serilog |
| Runtimes | .NET 8 |
| Tests / CI | good / CI in place |
| Last commit | 2026-06-15 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Payments and finance (system generated; curate in repo-owners.json to override) |
| Product area | Shared platform |
| Hosted | AWS + on-prem Ships artefacts to both AWS and on-prem machines (see evidence below)
|
| Releases | 1 release pipeline(s): \finance\payments\paymentprovider-br-dge-api CI |
| Integration | rest |
| Source | Open in Azure DevOps |
Risk flags
No risk flags recorded.
Each flag links to its glossary definition.
Dependencies in context
Entanglement
loose No binding mechanisms apply: this system needs no untangling work.
Depends on / used by
Migration playbooks
Generated from this repo's assessment data: what is feasible, what blocks it, and the steps in order. Ratings: green means actionable now, amber means sequence other work first, red means blocked, grey means not applicable.
ZDD adoption
No excuseNothing technical is holding this repo on the three-week release. It either already deploys without downtime (AWS) or is a modern, well-tested service the automated stealth path can carry today. Already deploys as a container to AWS, which releases without downtime today. Some artefacts still deploy on-prem; they follow the on-prem path. Separating it from the three-week release is a process decision, not a technical one.
- 1 system(s) depend on this repo; during a rolling deploy they will talk to old and new versions at once, so responses must stay compatible
- Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
- Make every change dual-version safe: backwards-compatible APIs (new major version for breaking wire changes), expand and contract for any schema change, and consumers tolerant of unknown fields.
- Audit serialized data: anything in Redis, queues or shared caches must deserialize cleanly across adjacent versions.
- Wrap behaviour changes in feature flags so code deploys dark and release becomes a business decision, not a deployment event.
- Route deployments through the Workflow Engine's automated drain, deploy, health-check, return cycle (the path proven by the first automated production run in mid-2026).
- Verify with area-scoped regression rather than the whole-platform cycle, and watch error rates after rollout with automated rollback on alert.
SQL Server exit
Not applicableNo SQL Server dependency is recorded for this repo. Nothing to migrate.
Containerisation
Partially containerisedPart of this repo already builds containers for AWS while other artefacts still deploy to on-prem machines. Finish the job by moving the remaining artefacts (see the hosting evidence on this page) through the same pipeline template.
- Identify the artefacts still deploying through deployment-group release pipelines (listed in the hosting evidence).
- Move each to the shared ci.yml pipeline template with the container parameters, as the already-containerised artefacts in this repo do.
- Disarm the old release pipelines once traffic is confirmed on the new deployment.
Recommended actions
No specific actions for this repo. It either needs only normal maintenance, or its work is covered by an estate-level action. See the full programme.
Assessment notes
paymentprovider-br-dge
Purpose
Adapter API that fronts the third-party BR-DGE (Comcarde) payment orchestration platform: makes payments, checks status, handles hosted-payment-page orders, tokenisation and 3-D Secure, and maps PSP responses (including Stripe) back into TC's common payment models. Supports Apple Pay/Google Pay and alternative payment methods.
Tech stack
ASP.NET Core Web API on .NET 8 with MediatR handlers, API versioning, Swashbuckle, Serilog, Scrutor and Nerdbank.GitVersioning. Cloud-native: AWS SDK plus TC.Persistence.DynamoDB for persistence.
Deployment
Container-first: build-containers.yml builds the API image (SonarCloud analysis) and deploys to AWS ECS in eu-west-1 via the aws-payments-tc-apps Terraform repo under the finance-payments namespace; build-packages.yml publishes model packages. One release pipeline (\finance\payments\paymentprovider-br-dge-api CI); release_count 1.
Dependencies
Internal shared packages (TC.Payments.Logging, TC.Payments.Models, TC.Persistence.DynamoDB, TC.Diagnostics.HealthChecks) whose source repos are not identifiable from included.json with confidence, so none are listed as internal repo dependencies. External: BR-DGE/Comcarde sandbox and live APIs (secure.comcarde.com), Stripe as an underlying PSP, Apple Pay and Google Pay wallets.
Data stores
AWS DynamoDB via TC.Persistence.DynamoDB (V2 repository with V1 fallback) for payment persistence.
Integration points
Inbound REST API for TC payment callers; outbound REST to the BR-DGE API. No message-bus usage found.
Code health
Four test projects (API, Application, PSP response adapter, plus a test base) — good coverage. CI with SonarCloud quality gates. Last commit 2026-06-15; actively developed. Backstage catalog-info.yaml present.
Modernisation risks
Minimal: modern .NET 8, containerised, AWS-hosted with IaC. Risks are third-party concentration on BR-DGE for payment routing and coupling to its API contract, rather than technical debt.