Release Notes

2025 Release Notes

 

Sandbox Release Date:  June 16th 2025
Production Release Date: July 7th 

• Hosted Forms will now have a drop down and optional fill for routing numbers when entering ACH account information
• Virtual Terminal will now support secondary ACH account number field for account number validation
• Transaction Reports smart search feature has been updated to allow the user to add all search criteria and use a "Search" button to complete the search
• AccountVault will now support alphanumeric values as part of the account holder name field for all vault record creation endpoints.
• The “Require CVV” setting no longer applies to terminal transactions. Transactions forwarded to terminals will work as expected when the “Require CVV” setting is enabled
• Batch close email templates now load in the dropdown list as expected, and users can now complete the process for batch close email notification setup
• Enhanced Internal Logging and Bug Fixes

 

Version v23.30.172-0

Sandbox Release Date:  March 12th 2025
Production Release Date: Est. March 25th Paya Connect User Interface/ Virtual Terminal

Paya Connect Sandbox and Paya Connect Developer Portal Multi-Factor Authentication

Users will receive an email with 6 digit MFA code to their registered email address when the below conditions are met:

• User is logging in for the first time
• User has been logged out for 15 calendar days

MFA Code will expire after 5 minutes. When users attempt to enter an expired MFA code they will receive an error message and a new code will automatically be delivered to their email.

 

Version 23.30.165

Sandbox Release Date:  january 14th 2025
Production Release Date: March 5th 2025 (includes release Items from Prior November 2024 and April 2024 Sandbox Releases)

• Updates to the code to ensure the “product_code”:”999999” is used correctly in the transaction to avoid the reject by TSYS.
• As part of the PCI 4.0 requirements, passwords must confirm to the following requirements:
  1. A password must have a minimum of 12 characters.
  2. Passwords must be alphanumeric in nature and be stored or transmitted with encryption.
  3. Passwords must be changed every 90 days and must not be a repetition of the previous four passwords.
  4. In scenarios where a password is generated for the user because the user is new or sometimes during a password reset, the generated password must be unique for every user and it must be changed after the first use.
• Alignment on all refunds to provide the original amount value for the total refund amount. This was not aligning consistently when selecting Refund form the Transaction Receipt
• Surcharge amount will zero out when processing a Debit Card from Paya Connect Virtual Terminal. This is a restoration of functionality.
• Surcharge amount will zero out when processing a Debit Card from PayForm. This is a restoration of functionality.
• As part of the authOnly, authComplete with Surcharge functionality that has been released to sandbox the exact 422 error is now displayed in the UI advising of an issue.  If a user attempts to submit an invalid amount to refund such as 0, the expectation is to receive an error message of ‘ Transaction amount must be greater than zero for the following actions: [sale, authonly, authcomplete, authincrement, debit, credit, refund, tipadjust]

2024 Release Notes

Version

Sandbox Release Date: November 19^th 2024
Production Release Date: March 4^th 2025

• Consumer Fee (Surcharge and Convenience Fee) Enhancement - The API will now support submitting transactions with a consumer fee using the actions AuthOnly and AuthComplete. Important Note: When performing an AuthComplete you are only required to submit the transaction_amount with the final total if it is the same as the original AuthOnly transaction. If the final transaction_amount is different, you must also submit the subtotal_amount, surcharge_amount, and tax fields as well, with all amounts updated. Otherwise you'll receive a 422 error response indicating the reason for the error.
• Consumer Fee (Surcharge and Convenience Fee) Enhancement - The API will return two additional fields, auth_aurcharge_rate and auth_surcharge_fee. These are only added to AuthOnly and AuthComplete API responses. Please disregard these fields as they are only being utilized for internal logging purposes.
• Postback Update - Previous Transaction ID - Some transaction responses via the postback service did not include a value for previous_transaction_id within the JSON data. It was simply populating as null. This has been resolved. If a transaction includes a value for previous_transaction_id the value will now be populated in the POST from the Postback service. Note: Postback must be configured for the Transaction resource in order to receive any postbacks for the Transactions Endpoint.
• Hosted Payment Page Enhancement - Required Fields - Hosted Payment Page (HPP) has been updated to reflect the field requirements setup within the merchant's location. If CVV is required, it will now be required for HPP. The same goes for Require Street and Require Zip. Merchants may need to educate their end users if they require those fields in the Paya Connect UI, but had not made them required within HPP previously.
• Enhancements to improve our Vault Migration Process.
• Enhancements Canadian L2/L3 Settlement Process.
• Restoration of Functionality - Cloud EMV Transaction Refunds - Attempting to perform a refund of these transactions caused "Error 0291" from our processor. Merchants have been forced to perform unreferenced refunds (blind refunds) for these transactions. This has now been resolved and merchants are now able to refund these transactions through the UI and API using the previous_transaction_id.
• API and UI Response Message Enhancement - When you receive a response for an authorization request (Sale, AuthOnly) the response will now include the exact code and response message from the processor for declines and "00" for approved transactions. This will be displayed within the response_message field within the JSON API response body as well as the reason field within the Paya Connect UI Transaction Detail page.
• API Enhancement Transaction Detail Record - subtotal_amount has been added to the transaction record when querying transaction records or a specific transaction_id from the Transactions Endpoint.
• Restoration of Functionality for QuickInvoices - Consumer Fee - When a consumer fee (Surcharge or Convenience Fee) is configured on a service utilized by a Quick Invoice (QI), the fee amounts will calculate properly when selecting between credit card and ACH payment methods within the QI user interface.
• Quick Invoice Update - Logic regarding single_payment_max_amount and allow_overpayment.
  • If allow_over_payment is set to false - the maximum payment amount (single_payment_max_amount) should equal the invoice amount.
  • If allow_over_payment is set to true - the maximum payment amount (single_payment_max_amount) is configurable through the UI under the payment max amount. The current default is "9999999.99".
• CC Transaction Summary Enhancement - The Paya Connect UI has been updated to include an export button on the bottom right to export the data to various file formats. This mirrors the functionality or other reports.
• CC Transaction Receipt Modal Update - When users attempted to click the "Refund" button within the modal it would fail to load the UI and the user would be unable to process a refund from this screen. This has been resolved. Users are now able to process a refund from the Transaction Receipt modal window.
• UI Enhancements to improve IAP configuration.
• Paya Connect UI - Transaction Details Screen - Resolved an issue where an end user was unable to use the option to "Run Again" due to the error "Subtotal amount cannot be empty or 0". End users are able now able to properly use the "Run Again" functionality.
• Quick Invoice (QI) Functionality Restored - 500 error when creating a QI, a QI would be created, but no email sent. This has been resolved. The QI is created, the email is sent, and there is no longer a 500 error.
• Maintenance Updates to improve Level 3 processing.
• UI and API Return to Functionality - Void Transactions - Attemps to void a transaction using either the Transaction Detail screen or via the API were failing for certain users. This has been resolved, and the functionality has been restored.
• Paya Connect Virtual Terminal (VT) - 400 Bad Request - When a user attempted to process an ACH transaction using the VT the transaction would fail with the error "400 bad request - Bin number not found" if the ACH account number was not within our credit card BIN table. This logic has been removed for ACH processing and transaction functionality within the VT has been restored.
• Account Vault UI Error - Console Error - When a user attempted to update a vault record within the Paya Connect UI and used Actions Button on the right side of the screen (Actions>Edit) they would encounter a console error when trying to save the changes. This functionality has been restored. Users should now be able to complete a successful update.
• Additional Maintenance and Service performed.

 

Version

Sandbox Release Date:  April 17th 2024
Production Release Date: March 4^th 2025

• UI updates to support Canadian Processing and configuration.
• UI enhancement - Transaction Details screen will display all linked refunds. This will be listed as Refund History.
• API enhancement - response_message API response field returned from a transaction request will include the value provided by the payment processor. This value is provided to Paya Connect by the payment processor in their status_message field. This will help to provide more details on decline and error transactions to the end user.
• Surcharge Compliance Enhancement - Due to a change in card brand rules, new surcharge configuration will be limited to a maximum of 3% on any surcharge transaction. Additionally, it can only be a percentage rate.
• Internal API logging updates.
• UI issue resolved - 500 error when attempting to resend batch close emails.
• API issue resolved - Queries against the Transactions Endpoint utilizing modified_ts set to custom would return zero results.
• UI issue resolved - ACH refunds from the Refund button on the transaction receipt modal failing with a 422 error due to a missing ach_sec_code.
• UI issue resolved - ACH refunds from the Refund button on the transaction details screen failing with a 422 error due to a subtotal_amount being submitted as "NaN".
• API issue resolved - ACH requests missing the *ach_sec_code, a required field, were returning with the error "failure while communicating with processor". This has been changed to the error 422: ach_sec_code cannot be blank.
• Require ACH SEC Code feature flag - The ACH SEC Code (ach_sec_code) will be a mandatory field for all ACH transactions by the end of Q1 2025. Because not all existing integrations are prepared to support this field, we have created a feature flag within production with this October 2nd 2024 release. It will default to false until the implementation period is over at the end of Q1 2025. At that time we will default the flag to on and no ACH debit request using PayForm or the Transactions Endpoint will be permitted without the ach_sec_code field with the appropriate value (ex. WEB, PPD, CCD, or TEL).
• API issue resolved - Using the terminal isOnline request would result in a 422 error due to a communication failure if the device is offline or not plugged in. In order to remain consistent with RESTful standards, this error code has been changed to 503.
• Sandbox Postback service issue resolved - Within the sandbox environment some postback requests were stuck in the new status. A cleanup function was updated to make sure this is no longer the case.
• Sandbox User permission enhancement - An update to user permissions will allow our suport team to be more effective in the sandbox environment.
• Additional security and compliance enhancements.

2023 Release Notes

Version

sandbox release date: November 2nd, 2023
Production Release Date: November 15nd, 2023

• Minor UI issue resolved for "Refund Transaction">"Available to Refund" not displaying correctly.
• Corrected API response for non-Level 3 Transaction IDs to the TransactionLevel3s Endpoint. Now returns proper 422 error response.
• Corrected AVS responses using address within Test Data
• Corrected issue with blind bankcard refunds causing 500 error response. These should now process the refund as expected.
• Updates to the SSL certificates.

 

Version v23.30.11

sandbox release date: September 25th, 2023
Production Release Date: October 18th, 2023

• Hosted Form Enhancements
  • reCAPTCHA Token Invalidation
    • The reCAPTCHA validation process has been enhanced to combat fraud activity on the Paya Connect Hosted Payment Pages
    • After a token is utilized for an HPP request, it becomes unusable and invalid. The end-user must pass a new reCAPTCHA test to acquire a fresh new token.
  • Parse rejected reCAPTCHA responses
    • If an end-user does not pass a reCAPTCHA verification, the HPP used to decline the transaction, would previously display an error message stating "CVV cannot be blank." A revised message now appears stating "Transaction failed: Suspected fraud activity."
• Vault Record Updates
  • To address card account updater accuracy, we identified an invalid certificate that caused inaccurate response messages
  • New certificates have been uploaded for the card account updater function. If a certificate becomes invalid, Paya Teams will receive an alert.
  • Recent updates have been implemented to maintain stability in account vault records and prevent paper trail errors in the card account updater service.

2022 Release Notes

Version 22.30.0 (Rolled back)

sandbox release date: TBD
Production Release Date: TBD

• Compliance and Security
  • No Compliance or security enhancements on this release
• UI improvements
  • Improvements to the Domain menu to imporvement configuration field for the Registration options.*
• API Improvements
  • API imporvements to support beter reporting for Card Account Updater logs 
• DB Improvements 
  • Improvements to the the Welcome Email template that was part of the 22.26.0 release.   
  • DB improvements to support beter reporting for Card Account Updater logs 
  • DB improvements to include all possible update and error codes for CAUs source.  
• Terminals 
  • Added new terminal configurations with new rules for contactless payments.  This new configuration will allow for contactless transactions upto $2000.

*we have a known defect in this release that doesn't allow for the creation of new domains from the Add Domain function, Domains can still be created from the location or via API.  

 

Version 22.12.0

sandbox release date: May 9th, 2022
Production Release Date: May 25th, 2022

• Compliance and Security
  • No Compliance or security enhancements on this release
• UI improvements
  • Post Back configurator options for Quick Invoice.
  • Allow Expired Token controls for Paya Admins
• API Improvements
  • Adding API elements to support future Paya Interchange Optimization Solutions.  This field on the product transaction (processor service) will have eventual UI elements.
  • API fields added to the location to allow a user with the proper permissions to toggle on and off whether a location will be able to import expired tokens.  The Default for this is No and a location will need to have the value turned on.

  • Improved rules around the Bill Payment/Recurring/Installment Flags that will allow the integrator to pass these flags from an outside Paya recurring solution.

  • Added an API element on the contacts endpoint to support flags for Auto-pay enrollment for future PayaGOV solutions.

• DB Improvements 
  • Adding database elements to support future Paya Interchange Optimization Solutions.  This field on the product transaction (processor service) will have eventual UI elements.

 

Version 22.09.0

Production Release Date: March 16, 2022

***UI and API elements of this Release were rolled back and will be released again on April 28^th***

• Compliance and Security work:
  • MasterCard compliance to allow IBAN Country Code to be included as part of the transaction payload. 
  • Node.js upgrades
  • General security updated to Clickjacking also know as “UI redress attacks
• Accountform/Payform improved
  • Added field values to Accountform endpoint to allow integrators to require street address and zip code with the require_street and require_zip fields.
  • Added the ability to require CVV on Payforms this can be done by selecting the option at the service level, or using the Require_cvv field in a payform request.
• API Improvments
  • Postbacks messaging API now supports Quick Invoice resource
  • Location level API controls to limit the import expired Credit Card for account vault tokens
  • Additional updates to support future changes to Quick Invoices ​​​​​
• UI Improvements
  • Require CVV in the Virtual Terminal improved to valid that entries are limited to 3 to 4 numbers.
  • Customer Portal option to Pay multiple invoices will now display a message when if the user select invoices with different payment options.  The message will advise that only the invoices with similar payment types will be paid. 
  • Country Code field added to the service hierarchy
  • Postback logs page improvements to support Quick Invoice postbacks
  • Messaging on payment type mismatch on multiple invoice payment
• New Feature
  • Post back configuration APIs now include an option to Quick Invoice Post back functionality; a resource for the Quick Invoice endpoint has been added to the post back configurator.

 

Version 22.10.0

sandbox release date: March 14th, 2022
Production Release Date: April 13th, 2022

• Compliance and Security
  • Certificate updates for future account updater work
• UI improvements
  • Post Back configurator options for Quick Invoice.
  • Allow Expired Token controls for Paya Admins
• API Improvements
  • Account Vaults endpoints configired to reference the allow expired tokens settings in at the location level.  
• DB Improvements 
  • Dynamic Tax Table built to support future Level 2/3 optimization work. 

 

Version 22.09.0

sandbox release date: February 24th, 2022
Production Release Date: March 16th, 2022

• Compliance and Security
  • Node.js software package upgrades
• UI improvements
  • Country Code field added to the service hierarchy
  • Postback logs page improvements to support Quick Invoice postbacks
  • Messaging on payment type mismatch on multiple invoice payment
• API Improvements
  • Postbacks messaging API now supports Quick Invoice resource
  • Location level API controls to limit the import expired Credit Card for account vault tokens
  • Additional updates to support future changes to Quick Invoices

 

Version

Production Release Date: February 16th, 2022

• Compliance and Security work:
  • PHP Software pack upgrades to support the most current version on PHP
  • Updates to PCONs’s AMI versions
  • Card Account Updater certificate updates
• New Feature
  • Host Payment Pages now support convenience fee/surcharge for both CC and ACH pages.
• Other enhancements
  • Continued work on Recurring Flags on single transactions
  • Fixes on to Paya Connect’s handling of Terminal CVMs in lower environments
  • ZGATE Papertrail loging updates as part of the Recurring and Bill pay feature work. 

 

Version 22.07.1

sandbox release date: February 14th, 2022
Production Release Date: March 16th, 2022

• Compliance and Security work:
  • MasterCard compliance to allow IBAN Country Code to be included as part of the transaction payload. 
  • Node.js upgrades
  • General security updated to Clickjacking also know as “UI redress attacks”
• Accountform/Payform improved
  • Added field values to Accountform endpoint to allow integrators to require street address and zip code with the require_street and require_zip fields.
  • Added the ability to require CVV on Payforms this can be done by selecting the option at the service level, or using the Require_cvv field in a payform request.
• UI Improvements
  • Require CVV in the Virtual Terminal improved to valid that entries are limited to 3 to 4 numbers.
  • Customer Portal option to Pay multiple invoices will now display a message when if the user select invoices with different payment options.  The message will advise that only the invoices with similar payment types will be paid. 
• New Feature
  • Post back configuration APIs now include an option to Quick Invoice Post back functionality; a resource for the Quick Invoice endpoint has been added to the post back configurator.

2021 Release Notes

Version 21.33.0

Sandbox deployment Date: August 23rd, 2021 
Production deployment Date: September 9th, 2021

​​​​​Bug Fixes

• Minor bug fixes to the Customer Portal UI for the Quick Invoice Multi-Pay feature.

Infrastructure

• Monthly Patching.
• Cipher Updates. (Production Release October 6th, 2021)
• Security updates to how Paya Connect handled EFT updates.

 

Version 21.31.0

Sandbox deployment Date: August 9th, 2021
Production deployment Date: September 9th, 2021

Enhancements

• Customer Portal:
  •  Additional work to update the UI to remove pay now options from the customer portal when the Hiding Blind Payments option is enabled at the contact, location, or partner levels.   
  • Added new feature for Multi-invoice payment.  When Customer Portal is enabled for a contact, the contact can login to pay invoices.  The Customer Portal Experience has been enhanced to allow the contact to select multiple invoices and submit a single payment option to pay all the invoices at the same time, without having to enter payment information for each invoice selected. 
• API
  • Added hide blind payment attribute to the locationinfos lookup response.
  • Added vt_require_cvv attribute to producttransactions endpoint.
  • Enabled quickinvoices endpoint to allow invoice’s item list to be updated after the invoice has been partially paid. 
• User Interface
  • Updated Merchant portal Add Contact page with a hide blind payment option.
  • Added feature to allow UI creation and editing of the Account Vault Postback Configurator.
  • Enabled Quick Invoice item lists to be edited after the invoice has been partially paid.
  • Added Require CVV Option to the deposit account VT settings

​​​​​Bug Fixes

• Updated Quick Invoice accepted file types for file upload in UI and API.

Infrastructure

• Updates to DB migration service
• Added delays to transaction flow and batch close so that sandbox behaviors match Production events
• Added test response for Processor timeout testing  

 

Version 21.21.0

Production deployment Date: July 21st, 2021

This deployment updated the API to allow integrators to create new Account Vaults using Cards have have expired. The code change disables a validation rule that rejects expired exp_date fields sent to the v2/accountvaults endpoint.

 

Version 21.20.1

Sandbox deployment Date: June 17th, 2021
Production deployment Date: June 17th, 2021

Rollback 21.20.0

 

Version 21.20.0

Sandbox deployment Date: June 4th, 2021
Production deployment Date:  June 9th, 2021

ENhancements

• Added the ability to configure postbacks for the Account Vault resource via the UI
• Added the ability to disable the "Blind Payments" feature within the Customer Portal at the Domain, Location, and Contact level

Bug Fixes

• Updated the Quick Invoice payment page to display only approved transactions in the Invoice Details tile
• Corrected an issue on the Quick Invoice payment page where the payment date was displaying one day prior to the actual transaction date

 

Version 21.16.0

Sandbox deployment Date: May 3rd, 2021
Production deployment Date: May 11th, 2021

ENhancements

• Added the ability to configure postbacks for the Account Vault resource via the API (UI is still pending)
• Made updates to the Quick Invoice payment page UI to be more responsive with large amounts of data
• Added the "Hide Customer Portal Blind Payments" feature configuration to the UI pages for Domains, Locations, and Contacts

Bug Fixes

• Corrected issues causing transmission issues on the TSYS EnsureBill interface for Card Account Updater
• Increased the transaction amount upper threshold to $9,999,999.99 for ACH transactions
• Corrected issue within PayForm UI causing trailing zeroes after a decimal to be dropped
• Updated the Quick Invoice payment page to allow alpha characters in the Driver's License Number field for ACH transactions
• Updated the batch settlement processes to include EMV Tag 84 for Discover transactions

 

Version 21.12.0

Sandbox deployment Date: April 5th, 2021
Production deployment Date: April 13th, 2021

ENhancements

• Updated the Card Account Updater interface certificates and transmission encryption type
• Implemented the new Quick Invoice payment page UI
  • Added the new Quick Invoice payment page link to the invoice notification templates (new format is "https://invoice.payaconnect.com/paymentui/quickinvoice?id={id}")
  • Added a function to redirect the existing Quick Invoice payment links to the new Quick Invoice payment page
• Added a "hind_blind_payment" attribute to the domains, locations, and contacts endpoints (boolean value)
• Updated logging levels and alert content for Batch Close functions

Bug Fixes

• Updated the quickinvoices endpoint to return a 422 http response code with  response message indicating that the "amount value must be numeric" when item list amounts contain non-numeric characters
• Updated the timeout value between the API and zGATE microservices to support locations with large batches

 

Version 21.09.7

Production Deployment Date:  march 8th, 2021

ENhancements

• Security updates to restrict connectivity to TLS 1.2 with defined ciphers (see API Reference section)
• Security updates to AWS Amazon Machine Image (AMI) policy
• Security updates to third party software packages
• New internal endpoint for Quick Invoice payment page
• New paymentsui endpoint to facilitate enhancements for Quick Invoice payment page (beta version)

 

Version 21.03.1

Production Deployment Date: february 23rd, 2021

ENhancements

• Security updates to microservices
• Certificate update for Ingenico Tetra devices in Sandbox
• Update ALB and NLB for all microservices

2020 Release Notes

Version 20.48.1

Production Deployment Date: december 7th, 2020

ENhancements

• Updated Account Vault Title to 64 characters
• Updated the API to accept up to 128 characters in the street address on the transactions endpoint
• Updated the billig zip code to accept international postal code formats for the transactions, account vaults, and contact endpoints (between 4 and 12 alphanumeric characters including dashes and spaces)
• Removed the email ID from all notifications
• Updated the AccountForm to allow for up to a 15 second time mismatch between client and server

Bug Fixes

• Corrected issues in PayForm where ACH fields were being added in error
• Updated invalid error messages

 

Version 20.39.0

Production Deployment Date: Unknown

ENhancements

• Updated Tax Settings configuration for Deposit Accounts to be more clear on when Sales Tax rules would be applied

Bug Fixes

• Resolved issue in Virtual Terminal where Sales Tax Amount would get deleted after entering a zip code

2019 Release Notes

Version 19.52

Production Deployment Date: December 23rd, 2019

Enhancements

• Can now filter by "Last Four", "Account Holder Name", and "Account Type" on the recurring list view    

 

Version 19.50

Production Deployment Date: December 9th, 2019

Enhancements

• Cardholders will no longer receive an email notification when a credit card transaction is run as AVS only

 

Version 19.48

Production Deployment Date: November 25, 2019

Enhancements

• BIN information will now be available when viewing a stored credit card and credit card transactions
• Billing Account field is now a type ahead for easier and more accurate selection

Bug Fixes

• Resolved issue where city field was not updating on account vault when changing billing address

 

Version 19.47

Production Deployment Date: November 18th, 2019

Enhancements

• Billing statements are now filterable based on whether or not an item has a cost

Bug Fixes

• Upload file links will now work when using IE11
• Adjusted installment recurring transaction count based on number of transactions run regardless of approval
• Required fields on HPP are now being enforced

 

Version 19.45

Production Deployment Date: November 4, 2019

Enhancements

• Added numerical value to card expiration date drop down menu

 

Version 19.44

Production Deployment Date: October 28th, 2019

Enhancements

• When creating a new recurring payment, the payment start day will now be blank by default.

 

Version 19.42

Production Deployment Date: October 14th, 2019

Enhancements

• Added ability for cardholder to save a new card when paying from a Declined Recurring email notification
• Updated error verbiage when hash key expires to be more clear
• Enhanced Location Billing Account logs to show additional fields
• Added measure to prevent real-time changes to role privileges; a "save" will now be required for the changes to take effect

 

Version 19.40

Production Deployment Date: September 30th, 2019

Bug fixes

• When a card type is disabled, a transaction can longer be run with a saved account vault of that type
• When a card type is disabled on a product, an account vault of that type can no longer be saved
• Quick Invoice items now display an ending 0 when viewing from the paylink

 

Version 19.39

Production Deployment Date: September 23rd, 2019

Enhancements

• Enhanced user experience by updating field name to "Billing Street Address" on AccountForm and PayForm.

 

Version 19.38

Production Deployment Date: September 16th, 2019

Enhancements

• Enhanced user experience so that fields requiring specific lengths cannot be saved unless correct when saving an Account Vault

Bug fixes

• Enhanced readability of the Authorization Agreement when saving an Account Vault from Cardholder Portal

 

Version 19.36

Production Deployment Date: September 2nd, 2019

Enhancements

• Enhanced Transactions Report with additional "Reason" columns

 

Version 19.35

Production Deployment Date: August 26th, 2019

Enhancements

• Enhanced user experience with additional action buttons on view and edit screens
• Enhanced user experience by adding "Created By" and "Created Date" as filters on Location Accounts list view

Bug fixes

• When skipping a payment on an Installment Recurring, the installment total count will be reduced

 

Version 19.34

Production Deployment Date: August 19th, 2019

Enhancements

• When viewing file names in the UI, special characters are now displayed as underscores
• Enhanced file uploading to allow for drag & drop

Bug fixes

• Transaction full details page now displays increment button for authonly transactions
• Quick Invoice can now calculate total when data format is not sent as expected

 

Version 19.33

Production Deployment Date: August 12th, 2019

Enhancements

• Enhanced user experience by adding navigation links when using list view
• Updated Cardholder Portal to include file attachments for Quick Invoice
• Enhanced notification field names for better user experience

 

Version 19.32

Production Deployment Date: August 5th, 2019

Enhancements

• Updated the user interface to make naming more consistent
• Additional user levels now visible in the user interface (UI)

 

Version 19.31

Production Deployment Date: July 29th, 2019

Enhancements

• Simplified Locations > General Info view by removing unnecessary fields
• Enhanced Stored Account page to show "Recent Transactions" and "Recurring Billings"
• Removed email notifications when submitting AVS only for an account vault

 

Version 19.30

Production Deployment Date: July 22, 2019

Enhancements

• Updated permissions so recurrings cannot be skipped or deferred by contact user

 

Version 19.29

Production Deployment Date: July 15, 2019

Bug Fixes

• When editing a Contact recurring, the default account vault will now stay the same unless explicitly changed.
• Account vault can now be saved from a terminal when running AVS only.

 

Version 19.26

Production Deployment Date: June 24, 2019

Enhancements

• Enhanced Billing capabilities, which include:
  • Increased flexibility by adding more billing items
  • Easier and more accurate pricing updates through the addition of pricing groups
  • Added ability to bill one location for a multi-location business through the addition of billing groups

 

Version 19.25

Production Deployment Date: June 17, 2019

Enhancements

• Added ability to upload files to Quick Invoice

 

Version 19.24

Production Deployment Date: June 10, 2019

Enhancements

• Enhanced recurring list view with additional filters and links
• When setting up a recurring payment, a contact record is no longer required when using a stored account

 

Version 19.23

Production Deployment Date: June 3, 2019

Bug Fixes

• When running AVS only on Virtual Terminal, transaction amount is no longer required
• When editing ACH product, MCC can now be entered

 

Version 19.22

Production Deployment Date: May 27, 2019

Bug Fixes

• Visually enhanced "Submit Payment" button on HPP for various browsers
• When filtering by Transaction Source on transactions, only exact matches will be returned

 

Version 19.21

Production Deployment Date: May 20, 2019

Enhancements

• Level 3 support now has the ability to see downstream request data to processor
• Enforced proper structure when adding a domain
• Added ability to deactivate developer id
• Added ability to change authorization verbiage on Quick Invoice when paying with ACH

Bug Fixes

• Enhanced user interface (UI) to remove actions the user did not have permissions for

 

Version 19.20

Production Deployment Date: May 13, 2019

Enhancements

• Updated menu labels for transaction reporting
• Invoice number is now editable in Quick Invoice

• Simplified recurring payments view for status

Bug Fixes

• Ingenico terminals can now reprint receipts

 

Version 19.19

Production Deployment Date: May 6, 2019

Bug Fixes

• Corrected errors in drop down options when using Mailbox Messaging

 

Version 19.18

Production Deployment Date: April 29, 2019

Enhancements

• Added device connection logs to UI
• Enhanced Token Sharing

 

Version 19.16

Production Deployment Date: April 15, 2019

Enhancements

• Enhanced HPP to allow for title and logo to be optional    

Bug fixes

• HPP form will now be responsive on mobile devices

 

Version 19.15

Production Deployment Date: April 8, 2019

Enhancements

• Added ability to see deleted services/products in batch tab under location

 

Version 19.14

Production Deployment Date: April 1, 2019

Enhancements

• Added asterisk on user setup to denote required fields
• Can now specify a custom name for a custom field on HPP. This will display in transaction reporting.

Bug fixes

• Room number is now visible on a transaction receipt for lodging merchants

 

Version 19.13 

Production Deployment Date: March 25, 2019

Enhancements

• Enhance user experience around managing merchant receipt logo

Bug fixes

• Users will land on specified default page upon login

 

Version 19.12 

Production Deployment Date: March 18, 2019

BUG fixes

• SSO integrations will ignore blank fields when updating a contact

 

Version 19.11 

Production Deployment Date: March 11, 2019

Enhancements

• Transaction reporting now displays origin of transaction
• Support level users can now remove email addresses from the local blacklist
• Enhanced accountForm/payForm to accept fields in payload on POST

BUG fixes

• First 6 of card number is now an option in transaction reporting
• Contact email address now populates when creating Quick Invoice
• Resolved various UI issues

 

Version 19.09 

Production Deployment Date: February 25, 2019

Enhancements

• Enhanced speed for recurring payments

BUG fixes

• Corrected rare instance when trying to save an account vault from the full transaction details page

 

Version 19.08 

Production Deployment Date: February 18, 2019

Enhancements

• Enhance Quick Invoice to reopen the invoice if the linked transaction is voided

 

Version 19.07 

Production Deployment Date: February 11, 2019

Enhancements

• Added ability to send merchant notification when quick invoice is paid
• Enhanced Quick Invoice to include a comments section on invoice

Bug Fixes

• Corrected calculation when refunding a transaction with a surcharge
• If surcharge is enabled, the surcharge amount is now visible in recurring payment email reminder
• When no receipt logo present, added transparent image for receipt logo so image doesn't show as broken
• Corrected signature image to display properly, including when printing

 

Version 19.06 

Production Deployment Date: February 4, 2019

Enhancements

• Enhanced Transaction endpoint to improve speed
• Improved terminal connectivity for Ingenico devices
• Enforced signature line being present on receipt when applicable

 

Version 19.05 

Production Deployment Date: January 28, 2019

Enhancements

• Modified selection filter list and added "Last 90 Days" 
• Added batch closure to postback options
• Enhanced terminal application to account for card removal at various stages

Bug Fixes

• Improved Ingenico terminal response at various stages of card removal
• Enforced scaling on signature images
• Enhanced landscape receipt view to include only wanted text
• Enhanced modal to add tags even if tag drop down is not closed
• Enforced location tree view to show properly in IE/Edge

 

Version 19.04 

Production Deployment Date: January 21, 2019

Enhancements

• Modified selection filter list and add "Last 90 Days" (UI)

Bug Fixes

• Fixed invalid javascript preventing acctForm/payform from work in IE/Edge
• Fixed duplication listing of Month/Year for exp date on acctForm/payForm
• Removed customer id field from Quick Invoice payment form
• Fixed Ingenico terminal prompting and receipt printing

 

Version 19.03

Production Deployment Date: January 14, 2019

Enhancements

• Added bin lookup endpoint to get bin detail from a previously run transaction
• Added buttons to top of forms as well as cleaned up title areas
• Added fields to set terminal timeouts on terminal pages

Bug Fixes

• Fixed bug that counted deleted HPP pages in total HPP allowed count
• Fixed event date filter on recurrings to show recurrings set to run the next day
• Fixed recurring to not allow mismatch between payment method on product and account vault (UI)
• Change text input for zip code to allow letters
• Fixed invalid formatting of numbers on dashboard graphs
• Fixed bug preventing locations from adding existing users

 

Version 19.02

Production Deployment Date:January 7, 2019

Enhancements

• Minor visual enhancements to the batch tab
• Visual enhancements and modernization updates to navigation menu

Bug Fixes

• Fixed recurring to not allow mismatch between payment method on product and account vault (API)
• Updated validation for forcing proper checkin and checkout dates in lodging
• Fixed recurring custom fields so they save properly when creating the record
• Added ability for location admins to view location tree

 

Version 19.01

Production Deployment Date: December 31, 2018

Bug Fixes

• Fixed incorrect validation preventing terminal transaction on payForm

2018 Release Notes

Version 18.52

Production Deployment Date: December 24, 2018

Enhancements

• Added ACH capabilities to Hosted Payment Page (HPP)
• Added ACH capabilities to payForm
• Added ACH capabilities to accountForm
• Added a "Back to Top" button for tall pages
• Added "Full Detail" button to transaction receipt and enhanced layout of full detail page
• Removed the words "Virtual Terminal" from every breadcrumb
• Added payment facilitator fields to product transaction (transaction service)

Bug Fixes

• Fixed user acceptance verbiage from disappearing after page refresh
• Fix bug in tags when voiding a transaction
• Added validation to gateway to prevent level3 data submitting tax exempt as yes along with tax amount

 

Version 18.51

Prodution Deployment Date: December 17, 2018

Enhancements

• Added security exception for livechatinc.com chat scripts

Bug Fixes

• Fixed logging when update_if_exists is sent in request to update a contact
• Fixed bug in transaction when terminal timeouts are not defined
• Updated messaging when deleting items on HPP design page
• Added validation to prevent duplicate items on Quick Invoice creation
• Removed menus when logged in contact users visit recurring declined payment page

 

Version 18.50

Production Deployment Date: December 10, 2018

Enhancements

• Added support for card_present flag
• Added debit option to account type filter in transaction listing
• Update UI defaults for checkin_date and checkout_date (one day prior)
• Added avsonly action to virtual terminal

Bug Fixes

• Stripped spaces when present in Canadian postal codes
• Fixed change logs from logging blank data on updates to product transactions endpoint
• Updated batch close summary notification template to allow easier customization
• Fixed erroneous error-logging in UI console

 

Version 18.49

Production Deployment Date: December 3, 2018

Bug Fixes

• Fixed Hosted Payment Page to work better in IE and Edge

 

Version 18.48

Production Deployment Date: November 26, 2018

Enhancements

• Added ability for locations to set default for recurring notification days

Bug Fixes

• Added prefill data for accountForm/payForm when provided in request

 

Version 18.47

Production Deployment Date: November 19, 2018

Enhancements

• Added validation to restrict level3 data from being submitted on debit transactions
• Added surcharge amounts and data to be available for use in email templates
• Added POST method for Hosted Payment Page
• Added POST method for accountForm and payForm
• Added code to show appropriate contact tabs when viewing/editing contact screens
• Added "sticky" headers to grid component for better viewing of long running lists

Bug Fixes

• Fix broken links for certain domains on quick invoice payments
• Allow ACH to be submitted without MICR data for an SEC of POP
• Fixed PO number from not displaying properly on some screens
• Fixed header and footer in UI from not displaying properly after browser refresh
• Fixed application error on transactions beta when filtering on a hidden column
• Fixed ach update script to better handle invalid data when batch processing status updates
• Suppress lodging specific data groups in settlement for debit transactions

 

Version 18.46

Production Deployment Date: November 12, 2018

Bug Fixes

• Change validation message on void to specify PUT instead of POST
• Updated middleware to allow multiple ACH terminal IDs in Sandbox for testing
• Fixed status column on recurring to not show "Unknown" for status
• Fixed level3 default calculations to better qualify