Designing a smoother, recurring payment experience for churches and educational institutions.

Overview

Many churches and educational institutions rely on consistent payments—whether it’s donations or tuition—to support operations and planning. However, both iOffering (donation platform) and iPayAcademy (tuition payment platform) originally only allowed one-time payments, requiring users to return each month and manually make payments again.
This friction led to inconsistent giving patterns and unnecessary workload for administrators.

TTo address this, I led the visual design and prototyping of a new recurring payment feature, rolled out across both platforms. While the feature logic remained consistent, I adjusted the UI/UX to fit the different use cases: donation for churches vs. tuition for academies.

The Challenge

"I want to support my church monthly, but I always forget…"
"Paying tuition every month is a hassle—I wish it was just automatic."

Both platforms lacked recurring functionality. Users wanted auto-pay features, while administrators needed tools to reduce tracking and follow-up tasks.

The Process

• Identified user/admin pain points through behavior analysis and internal feedback
• Set UX goals: automation, transparency, mobile-first design
• Designed a clean, minimal recurring payment flow for both user types
• Conducted testing and refined the experience for church members and parents separately

Design Solution

• Toggle between one-time and recurring donations
• Transparent confirmation and editable preferences
• Auto-reminders and billing visibility
• Integrated admin automation panel

Results

✅ Steady increase in recurring donations and tuition payments
✅ Significant reduction in admin tracking workload
✅ Higher satisfaction from both user groups (donors and parents)
✅ Improved competitive positioning with modern fintech-level UX

Tools

Figma / Visual Studio / Slack