backoffice-bt-credit-check
API that reports current credit levels for business-travel customers, calculating available credit to book and remaining credit to invoice from BackOffice data.
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 |
| Runtimes | .NET 8 |
| Tests / CI | some / CI in place |
| Last commit | 2025-06-27 |
| 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
|
| Releases | 2 release pipeline(s): \finance\backoffice-bt\backoffice-bt-credit-check CI; \finance\backoffice-bt\backoffice-bt-credit-check Stealth |
| Integration | rest, wcf |
| Source | Open in Azure DevOps |
Dependencies in context
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
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 guardrailsClose: 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.
- 5 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
- Consumes WCF contract packages: never take a breaking client bump mid-feature, and treat obsolete warnings as migration debt
- 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 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
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
backoffice-bt-credit-check
Purpose
Exposes business-travel customer credit information so any Phenix application (Booking Summary, View Credit Information, Invoice Wizard, Admin Studio) can display it. Implements the documented calculations: Available Credit to Book (credit limit + temporary increase − unpaid invoices − uninvoiced bookings) and Remaining Credit to Invoice.
Tech stack
.NET 8 / ASP.NET Core WebApi with Autofac DI, Asp.Versioning, Swashbuckle + NSwag client generation, StyleCop, Nerdbank.GitVersioning, TC.ConnectionBroker (Api, Wcf, HttpClient, Autofac), TC.Phenix.ApplicationFramework and TC.Phenix.Services.Client. Publishes TC.BusinessTravel.CreditCheck.Models as a NuGet package plus a generated WebApiClient.
Deployment
2 release pipelines under \finance\backoffice-bt\ (backoffice-bt-credit-check CI and a Stealth variant) fed by the backoffice-bt-credit-check CI build. CI uses shared InternalOSS/azure-pipelines-templates (dotnet 8.x). Per-environment appsettings cover QA, Training, Preproduction, Live, Production, DataFixQA, LiveProviderQA. Served at /services/backoffice-bt-credit-check.
Dependencies
- Internal: outbound WCF call to the legacy BackOffice booking service (
BookingServiceFacadeServiceClientoverIWcfConnectionBroker) for credit/booking figures, plus a brokered HTTPCreditCheckServiceClient; shared TC NuGet libraries. No estate repo mapped with confidence. - External: none identified (no third-party SaaS integrations in code or config).
Data stores
None owned by this service. Credit and rolling-balance data is fetched on demand from the BackOffice/booking service; a repository abstraction wraps that remote source rather than a local database.
Integration points
Inbound versioned REST API with Swagger/NSwag-generated client. Outbound WCF SOAP to the legacy BackOffice booking service and brokered HTTP to the underlying credit-check endpoint. Health checks probe the BackOffice dependency.
Code health
A single test project covering controllers, DI wiring, mappers, health checks, and the generated client. CI with shared templates, StyleCop enforced. Last commit 2025-06-27 — roughly a year without changes, so treat as stable/low-activity rather than actively developed.
Modernisation risks
Modern runtime, but functionally coupled to the legacy BackOffice WCF service for all data; it cannot be modernised in isolation from that dependency. Pinned older TC.ConnectionBroker 1.16.x and Phenix.Services.Client 7.x versions may need bumping alongside estate-wide library upgrades.