API changes:
- This change primarily focuses on altering the error response for invalid charge requests. As a result, the ‘resource.type’ field will now consistently contain a string value. Please take the enhancement into account during error mapping to avoid unexpected errors
Impacted Functionality: charge creation endpoint flows ( {{url}}/v1/charges ):
creating a pre-auth charge
creating a charge with an existing customer
creating a charge with an attached standalone fraud
creating a charge with an attached standalone 3DS
creating a charge with custom fields
- We have improved the Fee Profiles feature with a new validation within the API to allow positive amounts only when creating a Fee Profile rule.
- Extended our Database with some more UnionPay BIN ranges to make sure the system properly handles and returns the ‘card_scheme’ field.
- We have made the ‘card_name’ field optional for MPGS gateway charges. This change allows merchants to make the ‘card_name’ field optional for MPGS Gateway charges, aligning our system with MPGS documentation.
Impacted Functionality: charge creation endpoint flows ( {{url}}/v1/charges ):
- Direct charge with a card or vault token using MPGS as a gateway
- Pre-Auth charge with a card or vault token using MPGS as a gateway
- We fixed an issue where error responses in Vii’s balance check scenario didn’t populate the ‘status_code’, ‘status_code_description’, and ‘gateway_specific_description’ fields as anticipated. Please note that the response message from Vii’s service is mapped and stored in the ‘gateway_specific_description’ field, and the ‘status_code’ and ‘status_code_description’ fields will be null as expected. Populating gateway validation response, as per structure:{message: string,code: string,details: {path?: string,gateway_specific_code: string,gateway_specific_description: stringmessages: string[]} }
Impacted Functionality:POST {{url}}/v1/charges/balance
- Accertify Notifications – From now on, only the information about the latest transaction state and a charge ID are added to the Accertify notification when the request parameter ‘transaction_only’ is set to ‘True’.
- The ‘schedule.payment_date’ field is now used for checking the status of BSB charges made with Flo2Cash, as the gateway does not provide any other identifier.
- Mapped the Worldpay error code 103 to ensure that the right error message, “fraud_warning”, is shown to clients as against showing “unknown error” when the Worldpay gateway returns error code 103. Also, we mapped the Worldpay general error code category to ensure the appropriate error message is shown for the error codes returned by Worldpay.
Widget changes:
- We’ve fixed an issue where the Vault Display Widget didn’t display the “Show card number” button as expected. The issue occurred when following specific steps involving the Vault Display Access Token. Now, the widget functions correctly.
Impacted Functionality: The issue resided in the process of verifying whitelist IPs for all widgets utilizing the access token instead of the public key for widget initialization. In theory, this could impact clients employing the access token with the following widgets:
Simple Widget
Payment Source Widget
Visa-SRC - We enhanced the GooglePay workflow to ensure that the GooglePay button is displayed appropriately on Safari, Google Chrome, and other browsers.
