mytc-payments
Web application and API for taking customer payments through the version 2 MyTC customer portal, orchestrating card payments and back-office payment requests.
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, javascript |
| Frameworks | ASP.NET Core 6, Razor, gulp, NSwag 14 |
| Runtimes | .NET 6 |
| Tests / CI | some / CI in place |
| Last commit | 2025-06-30 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Agent tools and community (system generated; curate in repo-owners.json to override) |
| Product area | myTC |
| Hosted | On-prem Deployed to our own machines
|
| Releases | 1 release pipeline(s): \finance\payments\mytc-payments CI |
| Integration | rest, servicebus |
| Source | Open in Azure DevOps |
Dependencies in context
Entanglement
loosely attached Bound into the core by 1 mechanism(s).
- Pinning dependency: application-framework, mailtemplate-service
Detaches when its pinning dependencies are cut or multi-targeted (application-framework, mailtemplate-service).
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
A long roadTechnically eligible one day, but the blockers are structural: hosted WCF or SOAP contracts that cannot run two versions at once, or heavy legacy coupling. Sequence the modernisation work first. Legacy web front end: session state and framework age make mixed-version fleets risky until state is externalised.
- Serialized state or messages in flight (Redis or queues): new code must deserialize objects written by the previous version
- Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
- Raise automated test coverage first: ZDD trades the end-of-sprint manual gate for continuous automated confidence, so the tests are the entry ticket.
- 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.
- Externalise any remaining session state so users can move between nodes mid-session without disruption.
- 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
Ready to containeriseModern runtime, no hosted legacy transport: this service can follow the estate's proven container path (Dockerfile, shared pipeline template, ECS via Terraform).
- Add a Dockerfile and make the app read all configuration from environment variables and the secrets manager, never from machine-local files.
- Log to stdout and expose a health check endpoint so ECS can supervise it.
- Adopt the shared ci.yml pipeline template with the container parameters (awsRegion, containerAfterBuild, ecsTerraformRepo), which is exactly how the estate's existing AWS services deploy.
- Define the service in the Terraform repo, deploy to a non-production environment, then shift traffic and disarm the deployment-group release pipeline.
Recommended actions
Replatform mytc-payments to modern .NET
Runs on .NET 6, out of mainstream support. Blocked until stage 2 cuts: application-framework, mailtemplate-service.
Impact: Reduces the end-of-life runtime count
proposedAssessment notes
mytc-payments
Purpose
Payment-taking web app and API for the MyTC v2 customer portal. Renders hosted payment pages (Razor + gulp-built assets), generates payment deep links for the mobile app, and orchestrates payment requests against back-office and card-payment services.
Tech stack
Single solution (MytcPayments.sln) of .NET 6 projects: the MyTc.Payments ASP.NET Core web app plus facade/client libraries (BackOffice, CardPayments, ContactCentre, MailTemplateService, Quote). Front-end assets built via npm/gulp. NSwag generates .NET and TypeScript API clients at build time.
Deployment
One release pipeline (\finance\payments\mytc-payments CI) fed by the mytc-payments CI build; release_count 1. Build YAML (src/build.yml) uses .NET 6 SDK, npm install and gulp min steps on a self-hosted pool.
Dependencies
Internal (via NuGet packages/clients): TC.CardPayments.NetCoreClient.* (card-payments), TC.ConnectionBroker.* (tc-connectionbroker), TC.Exceptions.* (tc-exceptions), TC.Phenix.ApplicationFramework (application-framework), and a MailTemplateService facade (mailtemplate-service). Also consumes a Contact Centre API and a legacy MyTC Ops API via NSwag-generated clients. External: Firebase dynamic links for mobile app payment deep links.
Data stores
None directly; persistence is delegated to downstream back-office and card-payment services.
Integration points
REST clients to internal TC services (via ConnectionBroker); Azure Service Bus ingress client for card payments (TC.CardPayments.NetCoreClient.ServiceBusIngress); WCF support present via TC.ConnectionBroker.Wcf.
Code health
Unit test project present (tests/MyTc.Payments.Tests) with fixtures — some coverage. CI pipeline in-repo. Last commit 2025-06-30, actively maintained.
Modernisation risks
.NET 6 is past end of support (upgrade to .NET 8+ needed). Front-end relies on ageing gulp/npm build chain and MSBuild-time NSwag client generation, which couples builds to live swagger endpoints. Otherwise a reasonably modern codebase.