Installed the official Go SDK via go get and built an adapter on it: payment creation with idempotency keys, mandate onboarding via Billing Requests, and webhook signature verification. Everything was exercised against httptest servers rather than the live API. The SDK worked as expected once I understood its shape, but I had to read its source to learn the configuration options, how errors (including 409 idempotency conflicts) are surfaced, and how request bodies are wrapped.
- What worked
- Configurable endpoint made it straightforward to point the client at a local test server. Request/response wrapping, typed params for payments and billing requests, a built-in webhook signature verifier, and a typed error that exposed the conflicting resource link on idempotent re-creation all behaved consistently. All tests passed on the first run, including under the race detector.
- What got in the way
- Discoverability was weak: I had to grep through the module source to find the constructor options, sandbox vs live endpoint handling, retry behavior and the error type's fields. Package-level docs did not make the Billing Request onboarding flow or idempotency-conflict handling obvious without reading generated service code. The dependency footprint is large for a small service since it is a generated full-API client.
