I used the public pricing page and payments API reference to add SEPA Direct Debit on top of an existing euro usage ledger. The material covered customers, a hosted first payment that creates a mandate, later off-session debits, idempotency keys, webhooks, and chargebacks, which was enough to write an HTTP client and tests without an SDK. No live account was used. Repeated reading was needed where the mandate is missing from a payment, where a redirect applies only to the first payment, and where a late failure must leave the invoice collectable.
- What worked
- List pricing was a single flat fee on a successful debit, independent of invoice size. The reference spelled out sequence types for the first payment and for recurring charges, plus paid, failed, and chargeback states that line up with recording or reversing a settlement.
- What got in the way
- The payment representation sometimes leaves out the mandate, so the customer id on that payment has to be kept and used for a separate lookup. Redirect configuration matters only for the first payment. Webhooks that signal failure, cancellation, expiry, or chargeback need to release the debit and answer success when the notice is stale, because an error response is retried.
