Changelog – Release 66

API changes:

• Updated response error when DCI servers are unavailable. In the case when the DCI servers do not respond, we had the following response format:HTTP STATUS: 500{
"error_code": "InternalError",
"error": "Didn't receive the response from DPOP!"
}Now, it will start returning a 200 HTTP status with an exception described in the response body.The response structure will be as follows:{ "process_error_code": "tcp_error", "process_error_code_message": "Message with description"
• Implemented a new gift_card_number field for both Check Balance and Direct Charge requests for Vii service. This field is mapped with the Vii ‘CardNumber’ field from the request and contains the full gift card value.
• Added a new bulk_reference field for the new Split Payments functionality. The field will be also reflected in our Notifications feature.
• Adjusted GPayments mapping with the correct values and fields.
• Now, If the Paypal capture operation fails with the ‘CAPTURE_AMOUNT_LIMIT_EXCEEDED‘ error, the charge status will be ‘Failed’ instead of “Complete” as it was previously.
• Previously, when our system tried to get a transaction status for a direct debit charge and gets a 400 error – the transaction is treated as successful, and the status is updated to “completed“. This has been fixed, now the status will be failed for this scenario.
• Updated our API docs. Added a new Fraud endpoint for Split Payments functionality and added Fraud transaction type to the Transaction Types table.
• Updated the Timestamp format while sending payment results to Accertify. Timestamp for Sending transaction results to Accertify will be in the following format: yyyy-MM-dd’T’HH:mm:ssZ. The example: external_creation_date: “2023-05-21T23:59:56-0000”.

Widget changes:

• Fixed value of the status_code field for successful sale transactions completed using the Afterpay v.2.0, ApplePay, GooglePay, and PayPal wallets. Previously, after completing a successful sale transaction, the status_code field would have a “pending” value in the logs. Now this has been fixed and the status_code will have a “null” value in case of successful transaction.
• Check out our latest Client SDK version!