We have split payment and refund events.
Before, when a refund was added to the folio, you'd still receive the payment-posted event with the id of the refund.
Now, we have the following set of events:
payment-posted;
NEWrefund-posted;
payment-moved-from-folio;
NEWrefund-moved-from-folio;
payment-moved-to-folio;
NEWrefund-moved-to-folio.
In order to maintain backward compatibility, when a refund is created (moved), we emit 2 events, e.g.:
payment-posted;
refund-posted.
They will have the same entity id. So, if you've processed 1 event, you can skip the next one.
After October 21, 2020, we won't produce a payment event in addition to the refund event.
We have split payment and refund events. Before, when a refund was added to the folio, you'd still receive the
payment-postedevent with the id of the refund. Now, we have the following set of events:payment-posted;refund-posted;payment-moved-from-folio;refund-moved-from-folio;payment-moved-to-folio;refund-moved-to-folio.In order to maintain backward compatibility, when a refund is created (moved), we emit 2 events, e.g.:
payment-posted;refund-posted.They will have the same entity id. So, if you've processed 1 event, you can skip the next one. After October 21, 2020, we won't produce a payment event in addition to the refund event.
Don't forget to check the list of available events at https://apaleo.dev/guides/start/webhook/configuration#events