Release Date: September 17, 2024
URL: /packaging/installPackage.apexp?p0=04tOZ0000001pIDYAY
| Info |
|---|
Bug Fix |
Webhook Event
Parse the Payload of Charge Succeeded Webhook Event for BECS Debit only; exclude Credit Card to prevent duplicate Gateway Transaction
For Successful Payment:
If the payment is successful and the webhook is configured properly, the following records will be created:
A Gateway Event record is designed for the Charge Succeeded and Charge Updated webhook events.
A Gateway Transaction record is created/updated (if match is found) where the existing mappings are still applied and ensure there are NO duplicate Gateway Transactions records.
For Failed Payment:
If the payment fails and the webhook is configured properly, the following records will be created:
A Gateway Event record is created for the Charge Failed webhook event
A Gateway Transaction record is created/updated (if match is found) where the existing mappings are still applied
Make sure that there are NO duplicate Gateway Transaction records
For Pending Payment :
If the payment is pending and the webhook is configured properly, the following records will be created:
A Gateway Event record is created for the Charge Pending, Charge Updated and Charge Succeeded webhook events (there is a 3-minute delay for each webhook event)
A Gateway Transaction record is created/updated (if match is found) where the existing mappings are still applied
Make sure that there are NO duplicate Gateway Transaction records
For Payment Refund:
If refunding a payment and the webhook is configured properly, the following records will be created:
A Gateway Event record is created for the Charge Refunded webhook event
A Gateway Transaction (Refund) record is created/updated (if match is found) where the existing mappings are still applied
Make sure that there are NO duplicate Gateway Transaction records