A recent hotfix unintentionally caused duplicate payment records to be created for the same invoice when autopay-generated payments were manually processed. This led to confusion and potential risks, though no actual duplicate charges occurred.
What Happened:
- Manual processing of autopay payments triggered Beacon2 to create a second payment record.
- Duplicate records appeared in the system, raising concerns about double charges and increasing the risk of erroneous refunds.
- The issue was limited to specific organizations.
- No duplicate charges were confirmed in MerchantTrack.
Root Cause: Beacon2 created new payment records without checking for existing ones due to a missing PaymentID in the request payload. This behavior was introduced by a previous hotfix meant to address missing payments.
Fix Implemented: The system now includes the PaymentID in requests to Beacon2, enabling it to recognize and skip existing payments—preventing duplicate records.
Customer Guidance:
- No action is needed from customers.
- All duplicate records are being cleaned up manually.
- We’ve confirmed that no duplicate charges occurred.