PosiPay 0.107.3 - 0 0.107.4 (Patch Version)
What’s New
When a Gateway Invoice record is created or updated, the system takes the parsed invoice ID and maps it to the External Invoice ID field on the Gateway Invoice.
When a Gateway Transaction record is created or updated, and the charge webhook does not include any metadata, the system will automatically populate the Transaction Reference ID field with the parsed Invoice ID if the Transaction Reference ID is still empty.The Gateway Transaction’s Change Data Capture event has been updated. When a Gateway Transaction is updated or created, the system tries to link it to the correct Gateway Invoice. It does this in two steps:
First, it verifies whether there is an existing link between the transaction and the invoice. If so, it uses the invoice ID stored in the Gateway Transaction, and then the Gateway Transaction will be linked to the matched Gateway Invoice accordingly.
If not, it tries to match them using two external fields:
The Transaction Reference ID from the Gateway Transaction
The External Invoice ID from the Gateway Invoice
The length of the Result Code field on the Gateway Transaction has been updated from 30 to 100.
Previously, if the API callout to retrieve the invoice failed, it would attempt to create a Gateway Invoice. This behavior has been updated; no record will be created if the response fails.
All API callout requests in PosiPay have been updated to include a 2-minute wait time for a response from Stripe, ensuring they remain within Salesforce's allotted waiting time.