Why architecture matters here

Recurring fails on unclear mandate, missing dunning, and cancellation friction. Architecture matters because signed mandates + audit + user portal make it trustworthy.

Advertisement

The architecture: every piece explained

The top strip is main path. Mandate (signed) user consent. Schedule cadence + amount. Charge event. Success settlement signed.

The middle row is lifecycle. Dunning retry + notify. Change user-approved. Cancellation signed. Grace + retry policy.

The lower rows are ops. Compliance SCA/PSD2/KYC. Analytics. Ops — reporting + audit + portal.

AP2 recurring — mandate + schedule + dunning + change + cancellationsubscriptions safely with agentsMandate (signed)user consentSchedulecadence + amountCharge eventon scheduleSuccess settlementsignedDunningretry + notifyChange (amount / cadence)user-approvedCancellationsigned eventGrace + retry policyfinal statesComplianceSCA / PSD2 / KYCAnalyticschurn + ARR + failure rateOps — regulator reporting + audit + user portalrecovermodifyclosefinalcomplymeasuremeasureoperateoperate
AP2 recurring payments lifecycle.
Advertisement

End-to-end flow

End-to-end: user signs mandate for $9.99/mo. Monthly charge event fires. Success. Card expires next cycle; dunning retries + notifies user. User updates card. Success resumes. Later user cancels; signed cancellation event; grace period; access ends.