So far so good. I have two stories to consider:

1. User is deleting and adding the same SKU every 13 days - got it for free.
2. (After 14 days of using his account) user raises quota, then in 14 days he lowers it - got the "rised quota period" for free.

• Add some payment notification jobs/emails
• More on auto-top-ups and disabling mandates
• Added tests for two jobs
• Tests for Mollie wallet top-ups
• Rename templates
• Fix parse error
• Stripe: Webhook fixes, more tests
• Add todo

Maybe we should authenticate the user with IMAP instead? As far as I know the protocol spec. does not require authentication, but it recommends it.

This driver is not a high prio for us. Patches welcome.

Ok, I was testing a different case. However, this case also works with Kolab backend. I assume that you're using the database driver. Is it right?

Rebase

• Add Mollie/Stripe tests
• Browser tests, mollie/stripe
• More browser tests, make possible to run both stripe and mollie tests
• Silence more phpstan errors
• Use wallet's payment provider if exists instead of the default provider
• Support: Display auto-payment info
• Log failed payment responses

@bohlender As you can see here I use btn-warning for the Subscribe/Unsubscribe button, which makes the button orange. I found that yellow didn't work well for buttons. Maybe we should just not use btn-warning at all. Please take a look at https://bifrost.kolabsystems.com/T315890#2637686 for possible improvement. I'd like to know your opinion.

• Log failed payment responses

• Support: Display auto-payment info

It works for me with Kolab backend, although the event info dialog displays "Repeat: Every 1 month(s), forever ". When I edit the event Recurrence form looks correct and the event is displayed properly on the 3rd Thursday as defined. So, I see only a problem with the "Repeat" text not being complete.

• Add Mollie/Stripe tests
• Browser tests, mollie/stripe
• More browser tests, make possible to run both stripe and mollie tests
• Silence more phpstan errors
• Use wallet's payment provider if exists instead of the default provider

• Fix a typo

• Add Mollie/Stripe tests
• Browser tests, mollie/stripe
• More browser tests, make possible to run both stripe and mollie tests

Resolve merge conflict

• Don't invoke user update job on user setting that is not used by the backend
• Add tests for User::name()

• Remove lodash

• Tests missing forgot password and 2-fa on admin logon

It wasn't supposed to contain all these commits. Abandon. I'll create a new one.

Fix class name

One thing more. I think this table would also contain one-off bonus/penalty entries. So, that would be another reason why it should use negative amount values.