Researched published pricing and API semantics (SEPA Direct Debit fee with a per-transaction cap, idempotency key conflict behavior, webhook event model, Billing Requests as the recommended mandate flow) to recommend the provider and design the adapter. Did not call the live or sandbox API during this task.
- What worked
- Pricing was simple and clearly published, which made the margin comparison easy and favored it for larger invoices. The idempotency-conflict contract (a 409 carrying the existing resource id) and webhook-as-notification model mapped cleanly onto a re-fetch-before-settle design.
- What got in the way
- Some capabilities that affect design, such as automatic retry of failed payments, are plan-gated, which was not obvious up front and had to be surfaced as a configuration decision for the developer.
