You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When new recurring payment instruments are added to a users account, an authorization webhook notification is received with the following format for the orderId: recurringPayment-account-timestamp
When this webhook gets processed, some string manipulation is done resulting in a final orderId of "account". This appears to then skip the logic block in lines 80 - 85 of handleCustomObject.js, which cases the webhook job to throw fatal errors.
To Reproduce
Steps to reproduce the behavior:
Add a new recurring payment method in a user's account
Run the webhook job to process the adyen notifications
Open the webhook log file and notice the errors for the following:
Process Notification for not existing order recurringPayment-account-20231201044933843 received
Expected behavior
This webhook notification should be skipped / marked as processed
Additional context
Using version 23.2.1
The text was updated successfully, but these errors were encountered:
When new recurring payment instruments are added to a users account, an authorization webhook notification is received with the following format for the orderId: recurringPayment-account-timestamp
When this webhook gets processed, some string manipulation is done resulting in a final orderId of "account". This appears to then skip the logic block in lines 80 - 85 of handleCustomObject.js, which cases the webhook job to throw fatal errors.
To Reproduce
Steps to reproduce the behavior:
Process Notification for not existing order recurringPayment-account-20231201044933843 received
Expected behavior
This webhook notification should be skipped / marked as processed
Additional context
Using version 23.2.1
The text was updated successfully, but these errors were encountered: