Release 71
Production Release Date: 02/10/2023
Sandbox Release Date: 18/09/2023
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:
This modification affects several 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:
This modification affects several charge creation endpoint flows ( {{url}}/v1/charges ):
-
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: string
messages: 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.
Release 70
Production Release Date: 06/09/2023
Sandbox Release Date:27/08/2023
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.
Release 69
Production Release Date: 16/08/2023
Sandbox Release Date: 03/08/2023
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.
Release 68
Production Release Date: 26/07/2023
Sandbox Release Date: 11/07/2023
API changes:
Release 67
Production Release Date: 22/06/2023
Sandbox Release Date: 06/07/2023
API changes:
-
Improved error mapping for Afterpay gateway in case of timeouts to properly handle the service responses.
-
Fixed the EFTPOS connection workflow. Previously, to connect the gateway, the Merchant Name was supposed to be in the format MyMerchantName | Trans Desc | Trans 299. Now the format is MyMerchantName for this field.
Release 66
Production Release Date: 14/06/2023
Sandbox Release Date: 01/06/2023
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!
Release 65
Production Release Date: 24/05/2023
Sandbox Release Date: 10/05/2023
API changes:
-
Included reference and source_id fields for a scenario when creating a charge with a customer who does not have a default gateway.
-
Fixed refund error handling for FatZebra and Afterpay V1 where previously charge status would get stuck at the “refund_requested” phase.
-
We added a new card_acceptor.name optional field for EFTPOS payments. The EFTPOS service does not accept more than 40 characters for the card_acceptor.name field.
-
Improved capturing customer.payment_source.type in the logs when the charge is made with OTT or Vault Token.
-
Fixed the logic for switching between virtual and test modes for gateways that support these modes. Previously when performing API requests against the Virtual mode, gateways would switch to Test mode. This now should only happen when explicitly changing the mode.
-
Updated our API documentation with new meta.region value that allows setting region for Direct Debit business days logic.
-
Improved error message when canceling verification charge. Now, 400 status code and Invalid Operation for Verification Charge error message will be received.
-
Improved handling of the custom order_id and transactin_id for MPGS charges:
-
Now if a custom transaction_id value is provided in the void/cancellation request, it will be included in the URL parameter to MPGS.
-
Now the transaction_id character limit is 40. If exceeded, 400 status code and transaction_id/order_id must be shorter than or equal to 40 characters error message will be received.
Widget changes:
Release 64
Production Release Date: 21/04/2023
Sandbox Release Date: 13/04/2023
API changes:
-
We have improved the error mapping for the GPayments and Bambora. We have also improved the way we handle MPGS and Worldpay responses to make sure the provided information is full and corresponds to the description.
-
We have unmasked the Cardholder name for the Standalone 3DS logs.
Widget changes:
Release 63
Production Release Date: 03/04/2023
Sandbox Release Date: 16/03/2023
API changes:
- We have mapped the “cardholderAuthenticationResult” EFTPOS field with “transactions.cardholder_authentication_verification_value” Paydock field to make sure our clients receive full and proper information. Field params are described below:Field type: StringMin/Max symbols: 1Possible values:
- 0 – CAV not validated due to data error
- 1 – CAV failed validation
- 2 – CAV passed validation
- 3 – CAV validation could not be performed (Authentication attempted, but not completed)
- 4 – CAV validation could not be performed (System error or authentication failure)
- 5 – CAV not validated (Issuer is not a CAV service participant)
- 6 – CAV not validated (Issuer is not set to participate in any CAV service)
- We have increased the time for processing Direct Debit charges when the “503/504” status code is received to make sure those charges are handled properly and display the correct status.
- We have added the following additional fields to the logs to provide our clients with full and correct information on the processed charges:
- service_id
- service_name
- service_type
Those fields will store the id and name of the Fraud or 3DS service that is being used, and the service type (Fraud or 3DS). To test this new enhancement, it is required to create a standalone charge with a vault token and Fraud/3DS service and check the response.
Release 62
Production Release Date: 03/04/2023
Sandbox Release Date: 16/03/2023
API changes:
- We have improved the error mapping for the PayPal gateway. Now the “INSTRUMENT_DECLINED” gateway-specific code corresponds to the accurate error description: “The instrument presented was either declined by the processor or bank, or it can’t be used for this payment” in the Response logs.
- The “gateway_specific_description“, “error_message“, and “error_code” are displayed now after capturing the already voided and authorised Afterpay charge. To reproduce, the following steps should be taken:
- Create Afterpay charge;
- Void full amount;
- Try to Capture;
- Check the Response:
“type”: “capture”,
“status”: “failed”
Widget changes:
- Updated MastercCard logo, and implemented alerting and monitoring enhacements. Please make sure you Widget version is up-to-date!
Release 61
Production Release Date: 31/01/2023
Sandbox Release Date: 30/01/2023
Core changes:
- Improved the scheduler for authorised charges so that it doesn’t check the transaction status after the transaction was voided.
API changes:
- A new fraud operation mode called flex has been added to the fraud flows. It needs to be be accepted as fraud.mode charge overriding the service one:
POST v1/charges (or v1/charges/wallet)
{
…,
fraud: {
mode: ‘flex’,
…,
}
}
- Map response fields from MPGS 3DS transaction:
-
- gateway_specific_code = order.status
- gateway_specific_description = order.authenticationStatus
- error_message = transaction_declined
- error_code = gateway_specific_description
- Merchant Warrior error mapping improvement.
Widget changes:
- Validation for GooglePay wallet transactions has been updated. If there are an empty string for address_state field, the transaction will no longer result in a failure and will be processed based on the available information.
- Set up a delay for the AfterpayCheckoutButton to make sure the data is saved for further processing on the backend storage.
- Validation improvement for the cardholder field to make sure that correct information is passed in this field. This is being done to prevent issues such as card numbers being passed into the cardholder name field, or other unintended data being passed here.
Release 61 (Hotfix)
Production Release Date: 24/01/2023
Sandbox Release Date: 23/12/2022
Core changes:
- Validation enhancement for all the gateways to reduce processing time for subscription charges.
API changes:
- Fixed Get transaction status request for Merchant Warrior to receive appropriate information.
Release 60
Production Release Date: 12/01/2023
Sandbox Release Date: 21/12/2022
Core changes:
- Add Merchant ID and Merchant Website URL to the Request Headers for Afterpay v.2 service.
- Calculating transaction.remittance_date for EFTPOS virtual mode txns in a similar manner as on EFTPOS real environments to enable more efficient testing.
- Added the ability to overwrite the payment_source_information that had already been captured in the vault token but at the time of charge creation, some updated information has been processed either via customer payment source (If present) or input field payment source (If present).
- Added validation for total_refunded_amount field for all the payment services to make sure the refunds are processed properly.
API changes:
- Extend only_matched_transactions filter (“Filter transactions“ on UI) for transactions.remittance_date.
Release v1.84.1
Production Release Date: 12/01/2023
Sandbox Release Date: 08/12/2022
Core changes:
- Upgrade Angular version to latest stable v14.
API changes:
- Updated the EFTPOS CNP API paths from V2 to V3 (latest version).
- Added API requests for Webhook notifications templates.
- Extended webhook templates with Standalone Fraud check events: standalone_fraud_check_in_reviewstandalone_fraud_check_successstandalone_fraud_check_failedstandalone_fraud_check_in_review_approvedstandalone_fraud_check_in_review_declined.
Widget changes:
- Added a new validation for meta.hide_shipping_address field for PayPay Checkout. If the field has the value=false, the payments will be processed as usual.
- Resolved an issue with shipping.amount validation for payment wallets.
Release v1.83.1
Production Release Date: 08/12/2022
Sandbox Release Date: 24/11/2022
Core changes:
- Extended the flow for supporting Fraud check with Zippay and Afterpay v.2
- Added an option to utilise standalone 3DS with the Cybersource payment gateway
- Update Access level for SFTP service.
Release v1.82.1
Production Release Date: 10/11/2022
Sandbox Release Date: 10/11/2022
Core changes:
- Paydock Dashboard performance upgrade.
- Store customer.payment_source.card_number_bin for all successful and failed requests irrespective of the gateway.
API changes:
- Appending the API channel code to the acquiringInstitutionID while configuring the EFTPOS gateway which will allow a gateway to be sponsored by multiple acquirers.
Release v1.80.1
Production Release Date: 28/10/2022
Sandbox Release Date: 27/10/2022
Core changes:
- Add Error code and description for GPayments transactions.
- For the Gpayments client SDK, the secondary_url has been set to null.
API changes:
- Cardholder name will be sent as a part of every transaction captured in MPGS to ensure that this information is present in the transaction details.
Widget changes:
- Zippay redirect integration for Zippay widget.
Release v1.79.1
Production Release Date: 17/10/2022
Sandbox Release Date: 13/10/2022
Core changes:
- Extend the charges filter by transactions.type to support multiple values.
API changes:
- Standalone 3DS API documentation update.
