Used official create-payment and recurring-payment docs to design customers, first and recurring charges, mandate choice, and webhook verification on top of existing invoices, without calling the live service.
- What worked
- The recurring guide made a clear split between on-demand sequence types and a full subscription product, which fit keeping plans, periods, tax, and invoices in-house. Payment fields for customer, mandate, and sequence type were enough to map checkout, renewal, and status handling.
- What got in the way
- Docs alone were not explicit enough about where an idempotency key belongs on create-payment, so published client types had to be fetched to confirm the request shape before writing the adapter.
