Selected this vendor for bank payment submission plus statement retrieval and built an adapter against it. No public developer documentation exists, so no endpoint, authentication or payload shape could be confirmed; the adapter was written against a local interface with endpoint paths and header names driven by configuration rather than guessed constants.
- What worked
- The vendor's positioning around standard international payment message formats meant the file formats themselves could be implemented against open specifications rather than a proprietary schema, which is what made a usable adapter possible without access. A plain-file drop path could also be built as a day-one fallback.
- What got in the way
- Developer documentation is entirely gated behind a sales and onboarding process. There is no published API reference, no sandbox, no sample payloads and no error-code list reachable without a contract, so integration work cannot be de-risked or even estimated before signing. Every concrete detail had to be deferred to a single configuration surface, and nothing could be tested against the real service.
