Save payments and failed payments to database

Right now they are only tracked in logs and as a count on subscriptions. They are lacking timing information and more useful details such as error messages

No files, tests, or entry points are named. Trace where payments are logged and where subscription counts are updated, then determine the persistence design for successful and failed payments, including timing and error details. Done means both outcomes are stored with the requested information and existing payment tracking still works.

Written by the indexing model from the issue text.