Payment Groups

Challenge

Payment Groups replaced Anorbank's "My Home" section, a flat list of saved payments for utilities, car expenses, and subscriptions. The hard part was trust: letting users pay a whole group of transactions at once means every amount has to be visible, editable, and feel reversible — otherwise people simply won't press the button.

What shipped

• Templates: the old "My Home" list became one of the templates, and templates seed a new group with relevant transactions.
• Flexible batch payment: pay the whole group or only selected transactions, with the amount editable per transaction.
• Batch receipt: a new receipt type built for multiple transactions in one payment.
• Navigation and search: reworked category navigation and search across payments.

Testing

We tested in stages — corridor studies first, then rounds with real customers. Early rounds surfaced real resistance to paying a group at once; each iteration reduced it, and in the final rounds users completed group payments without hesitation.

Conclusion

Payment Groups shipped as the new home for all recurring payments, replacing "My Home" entirely; automatic recurring payments and fund reservation were planned as the next step. No single control solved the trust problem. Visible amounts, per-transaction editing, and the batch receipt worked as a set — and it took several rounds of testing to get that set right.