A recurring obligation is an amount or commercial duty that becomes due again according to a rule or agreement.
Examples include a monthly SaaS subscription, gym membership, rent, school-fee installment, association due or service retainer.
The obligation is not the payment
The obligation says what the customer owes. A payment attempt records one effort to satisfy it.
If the first payment attempt expires, the obligation still exists. If a later attempt succeeds, the same obligation becomes paid.
Why the distinction matters
Without a stable obligation, retries can accidentally create duplicate invoices, support teams can lose track of which period was paid, and reconciliation becomes transaction-led instead of customer-led.
What a recurring obligation normally records
- customer or account;
- billing period;
- amount and currency;
- due date;
- current commercial status.
Recurring does not always mean automatic debit
The commercial obligation can recur automatically even when the customer must authorize each payment attempt. The payment rail and authorization model are separate from the billing rule.
What creates the obligation
The obligation comes from the merchant's commercial rule: a monthly plan renews, a rent period begins, an annual membership falls due, or a school installment reaches its agreed date. The payment provider does not create that underlying commercial fact.
What can end or change it
Payment is one way to satisfy an obligation. The merchant may also cancel, waive, credit or adjust it under its commercial policy. Those outcomes should be represented explicitly rather than faked as successful payments.
Why one obligation can have several attempts
The customer might ignore the first request, cancel the second and complete the third through another enabled method. All three attempts refer to the same amount due for that billing period.
The useful states
- Due — amount is collectible.
- Paid — sufficient payment evidence satisfied it.
- Adjusted — amount or terms changed.
- Cancelled or waived — collection should stop.
Keeping the obligation separate from payment attempts is the foundation for safe retries, clean recovery and reliable reconciliation.
