feat: ideal topups

[stickyPiston]

closes #60

[TobiasDeBruijn]

Important note: We used to have one Mollie API key, we now have multiple:

• Koala
• Pretix
• Mongoose
  I think this will have to be changed in SadServer, but Mongoose should use the Mongoose balance in Mollie, and use the appropriate API key for it (from Mollie)

[stickyPiston]

What do you mean with mongoose balance in "but Mongoose should use the Mongoose balance in Mollie" exactly?

[TobiasDeBruijn]

So within our Mollie account we used to have just one 'Balance', which is a thing our users pay into. So if you pay your Koala activities, the money goes into that balance. Mollie then pays us that balance weekly (or whatever we configure).

This poses a problem for us treasurers. Every monday we need to split out this balance into it's separate components, currently only Pretix and Koala. However, recently I introduced two new balances: Pretix and Mongoose. This way, I get three seperate pay-outs every week, one for each product. This means I don't have to split it out manually anymore.

For mongoose (or Pretix), the only thing that changes is the Mollie API key used.

[stickyPiston]

Ahhh alright, the mollie api client only receives the api key that is configured in the .env file and does nothing with balances and whatnot, so i reckon that should be fine.

[TobiasDeBruijn]

Ahhh alright, the mollie api client only receives the api key that is configured in the .env file and does nothing with balances and whatnot, so i reckon that should be fine.

Yep that is fine! It's something to consider when deploying, though. The secrets probably still need to be created