Clear choice
One-time or monthly giving with plain language and no deceptive urgency.
Recurring giving is core to the product architecture, but this pilot site does not accept contributions. A real giving flow opens only after the required legal, fiscal, payment, accounting, privacy, receipt and solicitation controls are documented.
One-time or monthly giving with plain language and no deceptive urgency.
Receipts, preferences, service and impact updates after activation.
Consent-aware communication, easy preferences and suppression controls.
See preference-center demo →When giving is legally and operationally activated, a supporter should be able to view, pause, resume or cancel a recurring plan through a secure management link rather than having to call for routine changes.
Franklin Helps Main Product should use opaque plan references and leave payment credentials with the authorized payment provider.
A one-time supporter may eventually be invited to consider monthly support, but no prompt may imply giving is open before legal, fiscal, processor and solicitation gates are satisfied.
Current state: this is product architecture only. No recurring plan can be started, changed or charged on this pilot site.
After lawful giving is activated, recurring supporters should be able to use an expiring management link from a receipt to view, pause, resume, change or cancel a plan without creating a separate Franklin Helps password.
Payment success, failure and plan changes should arrive through a narrow provider event contract that rejects duplicate event IDs and keeps payment credentials outside Main Product.
Current state: no management link is live and no payment-provider webhook is connected.
A future payment-provider event must pass signature and duplicate checks before Franklin Helps prepares any supporter-service follow-up.
Failed-payment recovery should point the supporter to the authorized provider or a secure management flow; Main Product should not store raw card details.
Current state: no provider is selected, no webhook is live and no failed-payment message is sent.
Future recurring support is designed around explicit active, paused, canceled and past-due states so a supporter can understand what is happening.
The architecture supports secure management links tied to receipts or provider references without requiring Franklin Helps to store payment credentials or force a separate account just to manage a plan.
Current state: recurring donations remain closed and no payment-provider connection is active.
A supporter should be able to continue without identifying an employer. If they decline, Franklin Helps should not retain an employer reference merely to pursue a match.
Employer program rules change. A future match message should show only governed, checked program facts and should fall back to unknown or recheck-required instead of promising eligibility.
The product is designed for both one-time and monthly giving so Franklin-focused support can eventually be more dependable, while preferences, cancellation and supporter service remain easy to use.
See how future giving fits the model →