mandate_options configuration fragments for common billing patterns. They are passed as part of a first_in_series payment session request. See Quickstart: Recurring Payments for the full end-to-end flow.
Common Examples
Daily billing
A mandate authorising a fixed daily payment:Weekly billing
A mandate authorising one payment per week:Monthly billing
A mandate authorising one payment per month:Quarterly billing
A mandate authorising one payment per quarter:Annual billing
A mandate authorising one payment per year:On-demand (card top-up)
A mandate authorising merchant-initiated collections of up to 50.00 ZAR:on_demand mandates do not carry a recurrence. Payment methods whose consent surface requires an interval (such as Capitec VRP) are not eligible on on_demand. See the next example for the VRP equivalent of this pattern.On-demand (Capitec VRP top-up)
Capitec VRP does not support true on-demand collection; its consent surface always requires a cadence. Ascheduled mandate with a daily recurrence approximates it instead, authorising merchant-initiated collections of up to 50.00 ZAR on any day:
See Recurring Payments for how mandate type and payment method eligibility fit together.
Installment (periodic)
A mandate for 4 equal monthly payments of 250.00 ZAR, totalling 1000.00 ZAR:Installment (fixed)
A mandate for 3 payments on specific dates with a larger final payment, totalling 1000.00 ZAR:Some providers require a declared collection interval as part of consent registration. For
fixed terms, add a recurrence hint to terms to satisfy this requirement. It has no scheduling role: payment dates are still defined by items. The platform derives amount.max for provider registration from the largest amount across the installment items.
