Good morning All,
Can anyone help me with the Best Practice approach for backend server management of user payments. I’m just building a prototype app that requires the user to send ADA for service use. I’ve been looking through and testing the Cardano-Wallet API with a bespoke server wrapper enabling my client facing app. I’d like to know which of these is the best approach:
- Create a new wallet per client; although that entails the need management of all the keys generated, so that the wallets can be recoverable later (i.e. to avoid losing funds)
- Use a single wallet and provide the client a send address; however, I need to uniquely identify them. I can do that, by allocating the next unused payment address. However, given the standard, only 20 are preallocated, with more are only allocated when funds arrive; if the client doesn’t send money, I’ve got no way of generating more send addresses.Thoughts? Am I expected to dust them, although that could then be used as an attack mechanism to cost me money with skeleton accounts?
- Another way?
Any help/advice would be really appreciated.