API Enhancements:
- Implemented ability to attach a standalone 3DS charge with fraud to a Direct Charge
Implemented support for attaching Fraud Charge to Standalone 3DS and then performing the Charge by providing only the 3DS Charge ID.
Impacted Functionality: Charges
- Updated Zip URL endpoints and introduced the “reference” field for refund
Updated the Zip URL endpoints for sandbox and production to ensure that we are pointing to the correct URL advised by Zip, and also introduced & mapped the reference field as mandatory for the POST /refunds request body.
Impacted Functionality: ZipPay
- Renewed Click to Pay Sandbox and Preproduction environment encryption keys
Renewed Click to Pay Sandbox and Preproduction environment encryption keys to avoid service disruption when the encryption keys expire.
Impacted Functionality: Click to Pay
- Resolved misalignment between card expiry and token expiry dates in payment source object for standalone 3DS
Addressed the misalignment between the card expiry and token expiry dates in the payment source object for standalone 3DS and ensured that the card expiry date is the information displayed.
Impacted Functionality: Gpayment (Standalone 3DS)
- Introduced a flag in the SDK for the 3DS canvas widget to control the display of the messaging
The remote-app message was updated with an optional third parameter: when set to true, the “payment confirmed” message will be visible; when set to false, it will be hidden; and if the parameter is not provided, the message will default to visible.
Impacted Functionality: Gpayment (Standalone 3DS), Remote-app
- Addressed the incorrect “Stored_On_File” value passed for Charge refunds
Implemented a fix to ensure that the correct “stored on file” value is passed for charge refunds and aligns with the expectation from MPGS when a vault token linked with NT is used as the payment source.
- 1st Direct/Authorize Charge:
to_be_stored - 1st Charge Refund:
to_be_stored - Subsequent Direct/Authorize Charge:
stored - Subsequent Charge refund:
stored
Impacted Functionality: MPGS gateway
UI Enhancements:
- Removed Forwarding Institution ID from EFTPOS configuration (UI + API)
Removed the Forwarding Institution ID from the Create & Edit EFTPOS service to simplify merchant onboarding. Forwarding Institution ID is defined on environment level
Impacted Functionality: EFTPOS
