UI Enhancements:
- Updated the Gateway verification status to show ‘completed’
Enhanced verification status where a new column for MPGS has been added to show ‘completed’ instead of ‘n/a’.
Impacted Functionality: Reporting
- Enabled customer to configure a report when 3DS fields or card acceptor fields are selected
Fixed error where previously customers were unable to configure a Report when the 3DS fields or card acceptor fields were selected.
Impacted Functionality: Reporting
- Restricted the creation of charges, subscriptions and payment sources when PAN is present in the customer fields
Restricted the creation of charges, subscriptions and payment sources when PAN is present in the customer fields in the FrontEnd.
Impacted Functionality: Charges, Subscriptions and Payment Sources
- Removed console error in report creation page
Removed a console error that occurred when opening the report creation page.
Impacted Functionality: Reporting
- Enhanced browser zooming accessibility
Improved the visibility of page content at 200% zoom, particularly focusing on the Payment Activity graph on the Dashboard and ensuring a minimum height of 45%. This enhancement aligns with accessibility guidelines (1.4.4 Resize Text, AA), which improves the user experience for individuals relying on browser zooming.
Impacted Functionality: Dashboard
- Improved Token Management Permissions
Fixed an issue where previously users with the “Get current configuration” permission could interact with and change the “Auto Generate” toggle, contrary to expectations. This enhancement ensures proper access control by allowing users to view but not modify elements of the Vault Token Reference Configuration page. This prevents unauthorized changes and ensures data integrity.
Impacted Functionality: Company Permissions
- Fixed Broken Charges Template View
Implemented a fix to resolve the issue where the Charges Template view was broken and incorrectly displaying Vault token template names. This enhancement ensures the accurate representation of the Charges Templates, improving the user experience and facilitating smooth template creation without confusion.
Impacted Functionality: Charges Templates
API Enhancements:
- Amended the Afterpay v2 User-Agent Header from “custom” to “Paydock
Amended the Afterpay v2 User-Agent Header from “custom” to “Paydock” to ensure that Afterpay can identify the Afterpay v2 requests initiated by Paydock merchants.
Impacted Functionality: Afterpay v2
- Introduced an Afterpay v2 enhancement to support “popupOriginUrl”
Introduced support for the Afterpay v2 “popupOriginUrl”, and also set the value to https://static.afterpay.com for Afterpay v2 requests initiated through the Mobile checkout. This ensures that the requests are processed.
Impacted Functionality: Afterpay v2
- Implemented New-Relic monitoring for 3DS inbuild
Implemented support for the Inbuild 3DS performance to be monitored through New-Relic Monitoring.
Impacted Functionality: New-Relic request service tracking
- Resolved 500 error that occurred in the Paperless Gateway
Resolved 500 response code that previously occurred when a customer created a charge through the Paperless Gateway and used customer bank account data.
Impacted Functionality: Paperless Gateway
- Introduced new MPGS fields for card payments
Added new MPGS fields (card_funding_method, card_issuer and authorization_code) in charges.
Impacted Functionality: MPGS Gateway
- Implemented the differentiation between STORED and TO_BE_STORED payment sources
Implemented the differentiation between STORED and TO_BE_STORED payment sources based on Vault Token Flags.
Impacted Functionality: MPGS Gateway
- Added Vault_type in charge: services
Added Vault_type in charge: services where previously Vault_type was not captured.
Impacted Functionality: Charges
- Added Vault_type in charge: api-core
Added Vault_type in charge: api-core where previously Vault_type was not captured.
Impacted Functionality: Charges
- Fixed 500 error when deleting a transfer with an incorrect ID
Fixed 500 error when deleting a transfer with an incorrect ID to be shown as 400.
Impacted Functionality: Transfers
- Restricted the creation of charges, subscriptions and payment sources when PAN is present in the customer fields
Restricted the creation of charges, subscriptions and payment sources when PAN is present in the customer fields in the API.
Impacted Functionality: Charges, Subscriptions and Payment Sources
- Added vault token into the customer.payment_source for “check balance”
Added Vault Token as part a of customer.payment_source for “check balance”.
Impacted Functionality: Gift Cards
- Removed success operations from internal error log files
Removed success operations from internal error log files.
Impacted Functionality: Internal Logs
- Added card_used flag to the vault tokens
Implemented changes to align the communication of the MPGS field sourceOfFunds.provided.card.storedOnFile with the updated requirements. This enables more accurate handling of transactions with Paydock vault tokens by introducing new behaviour such as TO_BE_STORED and implementing the card_used flag. This enhances functionality overall and aligns with the MPGS requirements.
Impacted Functionality: MPGS Gateway
- Added vault_type field to charge logs from subscription
Implemented a new field, customer.payment_source.vault_type, in charge logs generated from subscription transactions with a permanent vault token. This enhances traceability and the completeness of logs. This improvement ensures that charge logs accurately reflect the vault type used during transactions, providing valuable visibility into payment source types.
Impacted Functionality: Charges, Subscriptions, Customers (Customer Create API endpoint)
- Resolved issue allowing the creation of customers with Session Vault as Payment Source
Previously, customers could be created with a Session Vault as a Payment Source without a gateway_id, leading to unexpected behaviour. With this fix, the request now fails with a validation error message, ensuring the proper handling and preventing the unauthorized creation of customers.
Impacted Functionality: Session Vault
- Resolved issue with Vault Token Reference (VTR) not saved into charges during In-build fraud and Standalone 3DS flows
Previously, VTR was not being saved into charges when used during In-build fraud or Standalone 3DS flows, causing data inconsistency. With this fix, VTR is now properly saved into charges in these scenarios, ensuring accurate tracking and reporting.
Impacted Functionality: Charges, Token Management
- Restricted Session Vault Token creation with gift cards and bank accounts
Implemented restrictions to prevent the creation of Session Vaults with gift card or bank account payment types, aligning with expected behaviour. This fix ensures data integrity and prevents the unauthorized creation of potentially invalid vault types, improving system stability and security.
Impacted Functionality: Session Vault Token
- Implemented card_used flag addition in Vault Tokens
Implemented a new feature to add a “card_used” flag in vault tokens created during one-time token flows with gateway IDs, ensuring clear differentiation between stored and to-be-stored payment sources. This enhancement improves the accuracy in data transmission to MPGS during payment sessions, and optimizes the overall system functionality and performance.
Impacted Functionality: MPGS, Vault token
