I’m sorry, but there’s no update to report on this yet. We’ve been busy working on other requests, but do hope to get to this in the future. We know this is important, and will update you here when we have made progress.
Please, please, please make sure you are PCI-DSS compliant. I cannot stress this enough!
I couldn’t recommend more highly that you do not save customers’ credit card information, even if you do this in PCI-DSS compliant manner. The fines you risk by doing this out of compliance are potentially huge ($5,000 to $100,000 per month until compliance is restored), and becoming compliant when saving card details is complex to achieve and maintain.
Hopefully you are already compliant, but I wanted to highlight this in case you were unaware and als ensure anyone else reading this is aware of the requirements too.
You can charge customers cards repeatably over time in a compliant manner if you get them to enter them online directly via our Stripe integration and charge them again using the Breww/Stripe integration. You should never know their card details throughout the process. More can be seen in this announcement post: Stripe card payments integration is now live! - Trade store payments & refunds (and more coming soon)