We’ve addressed an issue where some customers experienced duplicate payment records in Beacon, even though only one payment was processed through Stripe. These duplicates were caused by rare timing conflicts when Stripe retried a payment request.
What’s Changed
Beacon now includes a safeguard that checks for existing payments before creating a new one. This ensures that even if Stripe sends the same request more than once, only one payment record is created.
This update improves reliability and prevents confusion caused by duplicate entries.