Why did I receive a CONSUMPTION_REQUEST for the same transaction_id the day after I already received a REFUND for it? I received a CONSUMPTION_REQUEST, but due to a program error, I failed to submit the customer information. Later, I was notified with a REFUND, indicating that the transaction had been refunded. However, the next day, I received another CONSUMPTION_REQUEST notification for the same transaction_id.

We've observed two refund cases where we only received REFUND notifications without the expected CONSUMPTION_REQUEST notifications. Both cases came from the same user account. According to documentation, we should first receive CONSUMPTION_REQUEST before any REFUND notification. Has anyone encountered similar selective missing notifications? Could this be user-specific or related to particular refund circumstances? Environment: Production environment Valid server notifications setup (other notifications work fine) Only these two cases from same user showed this behavior