Subscription Inflexibility: Services like Spotify don’t offer long-term plans, making it hard for users to prepay for multiple years.

Unauthorized Charges: Users face random chargebacks or accidental charges from trials or untrusted platforms.

Group Payment Complexity: Splitting shared expenses (e.g., group subscriptions) is cumbersome without a centralized solution.

Set up payments for apps like Spotify with no long-term plans. Users send money to a card, stored securely, for fully automated multi-year subscriptions. Users are prompted to create a card, and after funding it, they can add subscriptions.

Once completed, they are directed to a page where they can view an overview, recent transactions on the card, and access additional details about it.

The challenge was that they handle third-party payments as funding sources, and I wasn't sure if I wanted to make my users do the same.

I realized that bypassing the fund card section and directly linking the one-time payment card to the user's personal account balance could significantly simplify the process, enhancing user experience and increasing the security of the product.

One of the challenges that made understanding Weave so difficult was the question of "Why"? For instance, why not just pool funds into one person's account instead of going through all this? It's a great question.

My answer lies in management. I once worked in an office where multiple contributions were happening simultaneously, and we used an app that facilitated this process. It was a lifesaver for the person managing the funds, as I mentioned earlier.

This experience led me to increase the number of cards a user can have on their account, allowing for the creation of multiple cards for various occasions.