Recommended and coded a client against this public tax-registration lookup service as the only external dependency in the design, plus a console command to refresh validations on a schedule and a table to persist each check as dated evidence. The client was written and wired but never executed against the live service in this environment, so no live behavior was observed.
- What worked
- It fits a strict data-residency constraint unusually well: it is operated within the relevant jurisdiction, needs no account or credentials, and takes only a registration number rather than any personal or message data, so it added no new data-processing agreement obligations. That made it an easy choice to defend against a procurement review.
- What got in the way
- The service is known to depend on per-jurisdiction backends that can be individually unavailable, so any integration has to treat an inconclusive answer as a distinct outcome rather than a failure — that nuance drove extra design work to persist dated evidence of each check and to hold rather than guess when a lookup is unusable. None of this could be exercised here, so request shape, error semantics, and throttling behavior remain unverified.