- Consent defines what the customer has agreed to: the amount, recurrence cadence, validity period, and maximum number of payments. For installment mandates, consent is structured around a total amount and a payment plan.
- Controls are optional fields that govern how and when payments execute under that consent, without changing what the customer consented to.
Consent
Define what the customer is agreeing to: amount, recurrence, validity period, and mandate type.
Controls
Govern how and when payments execute under a mandate without changing customer consent.
Use Cases
Common scenarios, such as subscriptions, debit orders, VRP top-ups, and usage-based billing.
Lifecycle
From customer consent through collection to termination: expired, exhausted, or cancelled.
Supported Payment Methods
See which payment methods support mandate-based collections.
Examples
Full mandate configuration examples for common recurring payment scenarios.