Repos / job-pending-receipts

job-pending-receipts

Console job that scans the last seven days of pending credit card receipts and voids any older than six hours, clearing receipts left hanging by abandoned payment sessions.

82 · greenlowloosely attachedOn-premZDD: ready with guardrailsjob

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.

Runtime currency / 25

Runs on supported modern .NET

Legacy transport / 15

Calls at least one legacy WCF endpoint

Test posture / 15

Some tests, coverage is thin

Security hygiene / 15

No credentials found in source

Dangerous coupling / 15

No dangerous coupling detected

Activity / 10

Last commit six to twelve months ago

Deployment hygiene / 5

CI in place

Health over time

No change since 2026-07-24 (82 to 82).

Facts

Languages	csharp
Frameworks	TC.MaintainanceTools.SimpleJobs 6, TC.ConnectionBroker 1.20
Runtimes	.NET 8
Tests / CI	some / CI in place
Last commit	2026-01-09
Owner	Owner unknown (mapping to be curated)
Domain	Payments and finance (system generated; curate in repo-owners.json to override)
Product area	Phenix
Hosted	On-prem Deployed to our own machines Release "\finance\jobs\job-pending-receipts CI": Staging: deployment-group phase (agents on our own machines) Release "\finance\jobs\job-pending-receipts CI": Staging: deployment-group phase (agents on our own machines) Release "\finance\jobs\job-pending-receipts CI": Production: deployment-group phase (agents on our own machines)
Releases	1 release pipeline(s): \finance\jobs\job-pending-receipts CI
Integration	wcf, rest, jwt
Source	Open in Azure DevOps

Risk flags

wcf-client hardcoded-service-identity

Each flag links to its glossary definition.

Dependencies in context

View in full graph

No internal dependencies, dependents or shared stores recorded for this repo.

greenamberreddata store (square, dashed link)Node size follows fan-in. Click any node to open it.

Entanglement

loosely attached Bound into the core by 1 mechanism(s).

Speaks WCF (client)

Detaches when its WCF surface gains a modern interface or its WCF calls move to one.

Depends on / used by

Depends on (0)

Nothing internal.

Used by (0)

No internal dependents.

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

Ready with guardrails

Close: the deployment path exists, but specific checks are needed first, typically raising tests, auditing serialized data, or respecting a shared schema with expand and contract. Test coverage is thin; ZDD shifts the safety net onto automation.

Dependencies and gotchas

Consumes WCF contract packages: never take a breaking client bump mid-feature, and treat obsolete warnings as migration debt

Steps

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.
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 applicable

No SQL Server dependency is recorded for this repo. Nothing to migrate.

Containerisation

Ready to containerise

Modern runtime, no hosted legacy transport: this service can follow the estate's proven container path (Dockerfile, shared pipeline template, ECS via Terraform).

Steps

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

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

job-pending-receipts

Purpose

Scheduled console job that queries pending credit card receipts over a configurable window (default: last 7 days), checks each transaction's session state via the payment router, and voids/deletes receipts older than 6 hours. Supports --env, --daysToCheck, --start, and --end overrides.

Tech stack

C# console app on .NET 8 built on the in-house TC.MaintainanceTools.SimpleJobs framework with async execution.
Clients: TC.Phenix.Services.Client 8.1 (booking service, receipt queries and void/delete), TC.Payments.PaymentRouter.Api.Client 2.5 (session state lookups), TC.Payments.JwtTokens with TC.ConnectionBroker AWS broker to mint JWTs for payment router authorisation.
Per-environment appsettings.*.json files; Scrutor for DI registration.

Deployment

Prod application with 1 release. Build pipeline job-pending-receipts (YAML build.yaml using shared InternalOSS/azure-pipelines-templates, .NET SDK 8.0.x) feeding release pipeline \finance\jobs\job-pending-receipts CI.

Dependencies

Internal NuGet packages: TC.Phenix.Services.Client, TC.Payments.PaymentRouter.Api.Client, TC.Payments.JwtTokens.*, TC.ConnectionBroker.*, TC.MaintainanceTools.SimpleJobs.*. The payment router API's hosting repo could not be confidently matched to an inventory repo name, so no internal repo dependency is recorded.
No direct third-party SaaS integrations; card gateway interaction is delegated to the payment router.

Data stores

None accessed directly; receipt data lives behind the Phenix booking service and payment state behind the payment router API.

Integration points

WCF to the Phenix booking service (ReceiptPendingQuery, void/delete of receipts).
REST to the payment router API (ExternalAccess_GetSessionStateByTxRef), authorised with JWTs created via the AWS-backed connection broker.

Code health

Unit tests present (PendingReceiptsJobTests, ArgumentOverridesTests) and template-based YAML CI. Last commit 2026-01-09.
Code is small and readable, though there is duplicated solution file layout (.sln at root and under src/).

Modernisation risks

JWT creation uses a hard-coded default company (UK) and a named default user GUID as the acting identity, which is brittle and an audit concern.
WCF dependency on the Phenix booking service ties it to that legacy surface.
Otherwise low risk: modern runtime, tests, and template CI.