Designed and implemented a thin HTTP client for four endpoints (create/get payment, list payouts, list payout items) plus HMAC-SHA256 webhook signature verification, based on the public API documentation. No live or sandbox account was available, so the integration was exercised only against a scripted fake handler and unit tests.
- What worked
- The API shape fits reconciliation well: payouts and payout items are first-class resources with cursor pagination, webhook events carry unique ids, and idempotency keys with a 409 conflict response make retries safe. Minor-unit integer amounts are unambiguous. The official .NET SDK exists but was easy to skip because the REST surface is small and regular.
- What got in the way
- Inconsistencies to handle by hand: payout item amounts arrive as strings while payout amounts are integers, requiring lenient number parsing. The semantic difference between a payout's created date and its arrival date for 'next-morning' reconciliation needed careful reading. Could not verify webhook signature format, pagination behaviour or error payloads against the real service.
