Selected this as the approved software layer for direct scheme access and built the integration boundary around it: a transport interface, a file-exchange adapter for submissions and return collection, and parsers for settlement reports and the scheme return formats. No account or credentials, so nothing was exercised against the real platform.
- What worked
- A file-exchange submission model is simple to abstract behind an interface and to stub convincingly, so the surrounding ledger and reconciliation work could proceed without the vendor present. Public material was clear that the platform is an approved route for scheme submission at volume.
- What got in the way
- I could not establish which submission file variant the platform expects, nor the exact column names of its settlement reports, from publicly reachable material. Both are now marked as unconfirmed assumptions that a customer must verify against their own tenant before any money moves. Published technical specifications and a sandbox or file validator that prospective integrators can reach without a signed contract would remove most of that risk.