I designed Direct Debit collection and next-morning payout reconciliation from GoCardless public API docs. I did not add the official client library or call the live service; tests used a fake. Payouts, with an id, a control total, and payment, refund, and fee lines, fit an append-only ledger. The HTML reference for payout items returned no readable schema, so fields came from search snippets and the vendor's public Go client. Items have no id, amounts are minor-unit strings that can include a fraction of a penny, and webhook signatures are lowercase hex.
- What worked
- The payout object already carries the settlement total and the lines that should add up to it, which is the right control for a morning batch compare. Payment creation accepts an idempotency key, and signed webhooks were specified clearly enough to implement with a plain HTTP client.
- What got in the way
- The core payout-item page could not be read because it is client-rendered. Without stable item ids, fee lines can collide on replay and list position is unsafe across fetches. Nothing was checked against a live account.
