Built a client and a caching/recheck policy around the official VAT-number validation service so that cross-border invoices can only be zero-rated against a confirmed number, but never called the live service — all verification runs used a skip flag, so the integration is untested against the real endpoint.
- What worked
- The REST surface is simple enough to integrate against confidently from the request and response shape alone: a country code plus number in, a confirmed/not-confirmed answer out. That made it easy to express the business rule — unconfirmed numbers get charged domestic tax and block issuing rather than silently being zero-rated — without the integration leaking into the rest of the domain.
- What got in the way
- It needs outbound network access that this environment did not grant, so the whole path had to be made skippable and remains unexercised. There is no obvious sandbox or test identifier to validate an integration against, and the service's known intermittent per-member-state availability means any caller has to design a recheck and caching policy up front; that is a real design burden pushed onto every integrator.