Changelog

• PRODUCTION RELEASE DATE: 04/12/2023
• SANDBOX RELEASE DATE: 20/11/2023

UI Enhancements:

• “Report delivery” tab

After requesting a report on the Charges page, you are redirected to the "Report Delivery" tab. This streamlines your settings adjustments, simplifying report customization.

Impacted Functionality: The UI of the Reporting feature.

• Add Gift cards to Smart Routing and Charge Reject

Smart Routing and Charge Reject configurations can handle gift card transactions. Create rules by adding "Gift Cards" as a payment source type to route or reject transactions, rerouting to the appropriate Gateway service. This ensures seamless processing.

Impacted Functionality: The “Gift Cards” payment source type is added to two Rule tabs: Routing and Charge Reject.

• VII Service setup: include the Gift Card option for Smart Routing

You can now input Gift Card numbers in the UI while selecting "by Smart Routing" during charge creation. This ensures smooth transactions with the Vii service.

Impacted Functionality: When you create a direct or pre-auth charge with "Add Charge" and select "by Smart Routing", you can enter the Gift Card number and PIN.

• Unable to edit subscription end date

We have introduced a fix to ensure the subscription end date is updated successfully when changed.

Impacted Functionality: Subscription charges

• UI - introduce "vault_type" in Apply Filter for the Vault page in the Dashboard

We have introduced "vault_type" as a filter on the Dashboard for the "Vault" page. This is so that you can filter for session and permanent vault tokens.

Impacted Functionality: Vault page

API Enhancements:

• [EFTPOS] Store correlation ID for all charges sent

This enhancement stores all correlation IDs for charges that are sent on to EFTPOS (all those that are not 5XX error codes) in the charge logs additional_params.correlation_id on the Java side.

Impacted Functionality: This does not impact clients.

• No validation for Store ID when connecting the Vii service

We have implemented an enhancement to handle specific scenarios during the Vii service setup. With this update, when you send all fields to connect to the service, we automatically remove records of any unused fields. This ensures a cleaner and more efficient setup process.

Impacted Functionality: The change affects the API part for the Vii service. When you connect the Vii service using all 5 connection fields (merchant_store_id, merchant_store_group_id, identification_code, acquiring_institution_id, and terminal_id), the system skips and does not save the identification_code, acquiring_institution_id, and terminal_id.

• 500 "Error checking payment status" when Creating Capture Transaction

Resolved an issue with the Stripe gateway, ensuring the successful completion of capture transactions.

Impacted Functionality: A 500 error with the message 'Error checking payment status' is no longer sent when processing capture transactions for pre-auth charges.

• Improve the error message for Zippay unsupported transactions

Disabled the option to capture or void a Zippay transaction for immediate payments(capture = true).

Impacted Functionality: Change applied on both UI and API. Zippay gateway - immediate payment flow.

• Introduce validation to block the exchange of OTT (gateway_id) into Session Vault Tokens

Introduced a validation to block the exchange of OTT with gateway_id into the Session Vault Tokens. This is because they are only applicable for payment flows where card details are not_stored.

Impacted Functionality: Session vault tokens

• Disable the ability to refund a pre-auth or create a pre-auth charge for gateways that do not support such actions

Blocked the ability to create a pre-auth charge for gateways that do not support it, and also blocked the ability to refund a pre-auth for gateways that support pre-auth charges.

Impacted Functionality: Pre-auth charges. Gateways impacted:

Afterpayv1, Authorize, Brain, Eway, Ezidebit35, Ezidebit, FatZebra, Flo2Cash, Forte, IpPayments, Merchantwarrior, Nab, Paperless, Payeezy, Paymentexpress, PaypalClassic, PaywayRest, Pin, PromisePay, Securepay, Sqid, Worldpay

• Restrict the ability to cancel a transaction for gateways that don't support “Cancel”

Blocked “Cancel” operation for gateways where “Cancel” is not supported.

Impacted Functionality: “Cancel” operation for charges

Gateways Impacted:

Afterpayv1, Authorize, Brain, Eway, Ezidebit35, Ezidebit, FatZebra, Flo2Cash, Forte, IpPayments, Merchantwarrior, Nab, Paperless, Payeezy, Paymentexpress, PaypalClassic, PaywayRest, Pin, PromisePay, Securepay, Sqid, Worldpay

• Card Acceptor fields absent in MPGS 3DS inbuild request to MPGS

We have introduced a fix that successfully maps the card acceptor fields to the MPGS order.statement descriptor fields when they are provided in an MPGS 3DS inbuild (with the fraud inbuild) flow.

Impacted Functionality: MPGS Gateway

• Enhancement - MPGS 3DS inbuild (send billing address fields to MPGS for 3DS authentication)

Introduced a fix to ensure that the billing information, such as the address city, address state, address country, and so on, is successfully mapped to the associated MPGS fields for the MPGS 3DS inbuild (with the fraud inbuild) flow.

Impacted Functionality: MPGS Gateway

• When using a session vault with MPGS in-request 3DS, storedOnFile is sent as STORED - it should be sent as NOT_STORED

Implemented a fix to ensure that "NOT_STORED" is the value passed in the "StoredOnFile" field to MPGS gateway for MPGS 3DS inbuild charge created using the session vault token.

Impacted Functionality: MPGS Gateway & Session Vault tokens

• Inability to process or decline authorised charge during fraud in review status

Implemented a fix to ensure that fraud can be processed or declined for an authorized MPGS 3DS inbuild (with the fraud inbuild) charge through the UI and API. This fix also ensures that the status in the Dashboard is accurate for such scenarios.

Impacted Functionality: MPGS Gateway

• Report Enhancements Output

Backend supporting the new “Report Delivery” Tab to simplify configuring reports.

Impacted Functionality: Reporting.

• Stripe Wallet Contract refactoring

Refracted the Stripe wallet contracts to align with the Paydock contract standards and created consistency among the wallet endpoints.

Impacted Functionality: Stripe wallets

• Paypal Wallet Contract refactoring

Refracted the Paypal wallet contracts to align with the Paydock contracts standard and created consistency among the wallet endpoints.

Impacted Functionality: Paypal wallets

• PRODUCTION RELEASE DATE: 13/11/2023
• SANDBOX RELEASE DATE: 30/10/2023

Release 73

API changes:

• Updated Spring Boot dependencies to the latest 3.x version

Impacted Functionality: Split Payments and Encryption Services.

• Hid permissions for metrics until they are deployed to production.

After a technical deployment during the last release, a few new permissions related to Metrics were added, but they were still not available for our users. This change is to hide these extra permissions until the functionality is fully available to our users.

Impacted Functionality: Permissions Management

• Introduced payment source "type" field in response to 3DS charge.

Ensure the 'payment_source.type' is displayed accordingly in response to a pre-auth 3DS charge.

Impacted Functionality: 3DS charge.

• Improved validation for card number field in charge creation

Enhancement to ensure that a body validation error is returned when a user attempts to create a charge using 'card_number' such as {{card_mpgs_sta10}}.

Impacted Functionality: Charge creation

• Included 'reference2' field in request to MPGS for charge with fraud inbuild

Ensure the 'reference2' field is sent in the request to MPGS for charges with fraud inbuild flow.

Impacted Functionality: MPGS transactions

• Removed Paydock phone validations from GPayments MicroService for Standalone 3ds

Ensure reliance is placed only on the GPayments validation for phone number.

Impacted Functionality: 3DS charges

• Fixed refund error for multiple capture transactions in Dashboard & API

Implemented a fix to support refunds for multiple capture transactions.

Impacted Functionality: Refund charges

• Corrected status display for companies' license transactions

Implemented a fix to ensure license transaction status = 'complete' instead of failed when funds have been deducted successfully.

Impacted Functionality: License transactions

• Vii gateway fields - Validation and Renaming Improvements

settings.acquiring_institution_id - field renamed, length validation added
settings.terminal_id - field renamed, length validation added
settings.identification_code - field renamed, length validation added
settings.merchant_store_id - length validation added
settings.merchant_store_group_id - length validation added

Impacted Functionality: Vii gateway fields

• EFTPOS gateway updates - Support for prepaidDebit BIN type

Support for the prepaidDebit BIN type with EFTPOS, along with various filter logic adjustments.

Impacted Functionality: EFTPOS gateway

• Added 'wallet_type' field to /charges/wallet endpoint for Apple Pay on Mobile

Ensure the wallet used for payment can be sent in the initialize wallet charge request.

Impacted Functionality: Wallet initialization

• Enhanced Paypal integration - Pass Partner BN Code in all API calls

Introduced the Bank Notation (BN Code) as a static header for all Paypal API requests to ensure Paypal can identify if the request is from a Paydock multi-tenant (Paydock_PSP) or from a CBA single tenant (CommonwealthBankofAustralia_PSP).

Impacted Functionality: Paypal gateway

• Webhook notification type improvement: "Standalone fraud"

Streamline webhook notifications by including only transaction-specific data, making the messages more concise and user-friendly.

Impacted Functionality: Webhook notification type: “Standalone fraud” passing transaction payload only instead of full charge logs.

UI Enhancements:

• Accessibility Enhancements

No functional changes applied.

Impacted Functionality: Front-End - Dashboard

• Improved UI message for report exports exceeding limit

This improvement provides a clear error message when exporting reports that exceed the limit, guiding users to utilize the 'Request report' option.

Impacted Functionality: If the scope of the filter exceeds 20,000 charges, the following error message displays: “The filter scope exceeds the export limit; please adjust the filter range or use the Request Report option for Charges”.

• Afterpay field validation for minimum_amount and maximum_amount

This release includes an improvement for the 'minimum amount' and 'maximum amount' fields in the Afterpay integration.

Impacted Functionality: In the ‘Edit’ Afterpay popup, the minimum_amount and maximum_amount fields now validate and display error messages if the fields do not contain numeric values.

• Hover to Split Payment tab

Added hover hints to the Split Payment tab when viewing bulk reference, ID, status, creation date, and update information.

Impacted Functionality: Front-end - Dashboard: Splint Payment tab

• Unable to Edit Gate

Ensured 'gateway label' via the UI could be updated without having to provide the credentials again

Impacted Functionality: Gateway configuration

• PRODUCTION RELEASE DATE: 02/10/2023
• SANDBOX RELEASE DATE: 18/09/2023

Release 71

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.

• PRODUCTION RELEASE DATE: 06/09/2023
• SANDBOX RELEASE DATE: 27/08/2023

Release 70

API changes:

• Implemented a new enhancement to handle the gateway error (400 Invalid Request Details) more effectively for PayPal transactions, specifically when updating `transaction_shipping_address` or `reference`.
• Enhanced the MPGS 3DS In-build flow by mapping the MPGS `transaction.reference` field to the Paydock  `reference2` field.
• Unmasked the `account_number` in the charge log when creating a charge through the following endpoints:

  `POST /charges`

  `POST /charges/direct`

  `POST /charges/authorized`

• Implemented an enhancement to handle pre-authorization charges for WorldPayWPG.
• Removed the `customer.payment_source.card_number_hash_uuid` field from the Accertify notification payload. This change applies when the request parameter `transaction_only` is set to `False`.
• Refined the error mapping for Stripe, enhancing the clarity of `generic_error` and other error messages.
• Updated error mapping for Pin Payments to improve accuracy and reporting.

• PRODUCTION RELEASE DATE: 16/08/2023
• SANDBOX RELEASE DATE: 03/08/2023

Release 69

API changes:

• Added the “order_id” or “transaction_id” fields for the MPGS charges created within the subscription. If the values are not passed by the customer, Paydock to auto-generate the value(s) and pass them to the gateway.
• Improved error mapping for Worldpay where the error codes and error descriptions were unknown.
• Remapped the gateway connection error from ‘Unauthorized’ to “Invalid Gateway Credentials” for MPGS.
• Now it is possible to assign the existing charge to a subscription using the:HTTP method: POST
  endpoint: /v1/charges/
  example payload: {"subscription_id": ""}
• Improved the error messages for MPGS capture transactions.