Release Notes

May 30, 2018 - Build 2.1.41

Improvements

  • The Real-time HTML API now accepts ‘ApprovedURL’ and ‘DeclinedURL’ as valid field name substitutions for the less concise ‘ThanksURL’ and ‘NoThanksURL field names.
  • All users may now view all Merchant Tools screens in French, by selecting ‘Français’ as your Language within the User Management screen and saving your user settings.
  • All PSiGate APIs now allow merchants to indicate whether their authorization requests involve card information that the merchant has securely stored as permitted by the cardholder and whether the request is the first time the merchant has been permitted to use the card for a future transaction or a subsequent use of the card.
  • The ‘Recurring?’ prompt displayed when merchants attempt to create an Immediate Charge within Merchant Tools has been replaced with an information box that gives VISA’s definition of a recurring charge.

Bug Fixes

  • Fixed a bug that allowed users to add cards to customer accounts without first inputting an expiration date.
  • Fixed a bug that allowed orders to process further actions after the order had been voided.
  • Fixed a bug that prevented merchants from being able to partially confirm pre-authorized invoices using the prescribed INV22 action as described within the Account Manager API.
April 10, 2018 - Build 2.1.40

Improvements

  • The iframe that displays a card issuer’s 3D Security page during a PSi3D API authentication request has been resized and made scrollable to accommodate pages that do not meet the iframe specifications.
  • The Shipping Name field is now included within the Order details page of the Merchant Tools interface.
  • Merchants are now able to specify, through a Merchant Tools or Realtime API transaction request, whether card details supplied within an order are stored and if the transaction is the first or subsequent charge made using those card details.
  • The settlement records within the Settlement Details page now sort by Entry Date by default.

Bug Fixes

  • Fixed a bug that caused our fraud prevention same card or same ip velocity check counters to increase when secondary card actions such as PostAuths, Refunds or Voids were performed. The velocity checks are only meant to prevent fraud associated with primary card actions associated with Sale or PreAuthorization requests.
  • Fixed a bug that prevented the action INV22 (Post-authorization of one or more previously authorized invoices) from functioning properly within the Account Manager API.
  • Fixed a bug that caused an error to be generated when apostrophes are included within authorization requests.
  • Fixed a bug that allowed split-funding instructions using a Realtime API to be sent within PreAuth requests instead of within PostAuth requests as intended.
  • Fixed a bug that prevented merchants from enabling Verified by Visa and Mastercard SecureCode from within the HTML Card Collection Settings page of the Merchant Tools interface.
Feb 26th 2018, - Build 2.1.39

Improvements

  • Removed the Forced Confirm button from displaying within the Confirmed screen of Merchant Tools for all merchants that have not requested and received permission to process, Forced Post Authorization requests.
  • Added the Search by OrderID function to the list of searchable parameters within the Confirmed screen.
  • Added a checkbox within the Create Charge screen that allows merchants to identify immediate charges as recurring.
  • Added the ability for merchants to partially refund orders with split-funding instructions from the Order Details and Confirmed Orders screen. Please note that these orders may only be refunded until a refund is successfully settled. Additional refunds will need to be processed offline.

Bug Fixes

  • Fixed a bug that caused refund transactions of orders with split-funding instructions and self-defined OrderIDs to become blocked.
  • Fixed a bug that prevented refund transactions of orders with split-funding instructions from reporting the updated balances of each split-funded store.
  • Fixed a bug in our Staging environment that caused real-time HTML Account Verification requests (PreAuths with a FullTotal value of ‘0’) to fail.
  • Fixed a bug that caused the Send Email Receipt function within the Actions dropdown menu of the Order Details screen to fail for some merchants.
November 28th, 2017 - Build 2.1.15

Improvements

  • The Visa Debit logo now correctly appears within the Invoice Details screen when the card charged is a Visa Debit card.
  • Merchants that use PSiGate’s hosted checkout page may now force the AVS or CVV2 fields to be mandatory by setting the Auto-Decline by AVS response code “V” or the Auto-Decline by Card ID response code “S” to decline.

Bug Fixes

  • Fixed a bug that prevented Visa Debit transactions from being properly voided after they are declined as a result of triggering an Auto-Decline check.
  • Fixed a bug that caused Verify Account requests (PreAuths for $0.00) that fail Auto-Decline checks to attempt to refund the associated order (which cannot happen because the order hasn’t been confirmed) instead of simply returning a decline response to the merchant.
September 28th, 2017 - Build 2.1.14

Improvements

  • Credit card validation has now been added to the hosted checkout capture page supported by our Real-time HTML API.
  • The Action fields reported within the various Orders screens now distinguish between Account Verification (PreAuth amounts = 0 dollar) requests and Pre-Authorization (PreAuth amounts > 0 dollars) requests by listing them as ‘Verify’ and ‘Reserve’ respectively.

Bug Fixes

  • Fixed a bug that caused certain CustomerIDs to be truncated.
September 9th, 2017 - Build 2.1.13

Improvements

  • Added additional fields to the list of those that may be echoed back within the Real-time HTML Hosted Capture page. Refer to the Real-time HTML API.
  • Added the ability for users to search by Customer Name from within the All Transactions page.
  • The Action field of Account Verification transaction requests is now listed as “Verify”.
  • Extended the Expiry Year list within the Real-time HTML Hosted Capture page to include the current year plus 10 years (ie. 2017-2027 inclusive as of the writing of these release notes).
  • Updated our Monthly Merchant Statements to include a store’s effective MDR.

Bug Fixes

  • Fixed a bug that caused charges created using the “Immediately” interval from displaying “Immediately” within Interval field of the Charges Summary screen.
June 27th, 2017 - Build 2.1.12

New Features

  • The Hosted Checkout Page merchants display to their customers through the Real-time HTML API can now be displayed in French by including a value of "FR_CA" within the "CustomerLanguage" element sent within Real-time HTML API requests.

Improvements

  • A "Refund Comments" place holder has been added to the field intended to collect that information when merchants refund their customers through the online Merchant Tools.
  • Action descriptors such as "Sale" or "Refund" now replace the numeric Action codes that were previously reported within transaction export files.
  • The Reserved screen is now sorted by Date by default.

Bug Fixes

  • Fixed a bug that prevented recurring charges created with an annual interval from creating an invoice on the date they were created.
  • Fixed a bug that could cause two refund requests to be processed when users attempted to refund an invoice from the Invoices screen.
June 4th, 2017 - Build 2.1.11

New Features

  • To ensure the bank accounts of Interac Online customers are not at all affected when the customer’s browser session inadvertently disconnects during Interac Online transaction process, the Realtime HTML API has been modified to allow Interac Online merchants to specify that they will confirm their IOP transactions themselves instead of relying on PSiGate to confirm their transactions.
  • A new Interac Online Self-Confirmation API has been developed to allow merchants to send IOP confirmation requests, which if approved, will charge their customer’s bank account.

Compliance-related Improvements

  • Implemented controls to prevent the processing of Force-PostAuth requests submitted by merchants that have not been authorized to send Force-PostAuth requests. Merchants that have a compelling business reason to process Force-PostAuth requests are encouraged to contact merchant.services@psigate.com.
  • Updated text and logos throughout PSiGate’s website and Merchant Tools user interface to meet Mastercard’s new digital brand requirements. Click here to view the new brand MC requirements.
  • Merchant Tools has been updated to accept MC 2BIN cards for all functions the input of a credit card number.

Improvements

  • The Customers summary screen has been modified to display only active customers by default.
  • Within the Customers summary screen, users may now search customer records by the date they were added.
  • Additional charge items added to an existing charge are now automatically enabled by default.
  • Order Verification requests that reference an OrderID that is associated with multiple authorization requests, now displays the order details and status of the most recent declined or approved request associated with that OrderID.

Bug Fixes

  • Fixed a bug that prevented users with the View User Log permission from viewing all user logs associated with their CID.
  • Fixed a bug that could cause two refund requests to be processed when users attempted to refund an invoice from the Invoices screen.
May 1, 2017 - Build 2.1.10

Improvements

  • We now prevent card holders using the Hosted Checkout page’s Masterpass service from selecting card brand types (Visa, MC, etc.) that the merchant does not support.
  • Added a “Caps lock is ON” message to our Merchant Tools login screen.
  • Added “Back to Customer” button to all Invoice screens accessed from the Customer Details page.
  • Changed the Merchant Receipt FROM address of all merchants where the value was set to NULL to donotreply@psigate.com to prevent the rejection of merchant email receipts due to email masking.
  • Added Sales and Refund summary totals to the Settlement Summary screen.
  • Added additional order validation to the Create Order screen to prevent merchants from encountering errors that would force them to input their order and payment information again.

Bug Fixes

  • Fixed a bug that prevented fraud rules from being applied to Customer IP addresses using the IPv6 format.
  • Fixed a bug that allowed non-alphanumeric characters to be included within authorization requests sent to Rapid Connect.
  • Fixed a bug that prevented users from being able to flag orders from the Order Details screen.
  • Removed the long number format from the Trigger Date column within the Charges screen.
  • Fixed Unit and Sales Total column miscalculations which occurred within the Settlement Summary screen.
  • Fixed rounding issues that occurred when orders were refunded multiple times.
  • Fixed a bug that caused the Amount field to display a rounded value when viewed through the Safari browser.
March 27, 2017 - Build 2.1.9

New Features

  • Merchants may now delete a credit card saved within a customer account and immediately assign another card to the customer’s charges that previously referenced the deleted card.
  • PSiGate is now able to communicate with you through notifications displayed within a Notifications Page accessed by clicking on an alarm icon in the top-right of the online Merchant Tools interface.

Improvements

  • When ISO users view user logs for a merchant, the logs now only show the user logs of the merchant that they have selected instead of showing user logs for all merchants that ISO user can view.
  • When users navigate away from viewing the details of a customer, a “Back to Customer” button is now displayed within destination page that will allow the user to go back to the details of the customer they were previously viewing.
  • Added a “Search by Date” function to the Charges screen.
  • Added LIKE search functionality to the Search by Company Name, Phone Number, and Email Address fields within the Customers screen.
  • The Amount field is now a field included within the Charges screen and its CSV report.
  • The Comments field is now returned within the CSV reports generated from the All Transactions or Declined screens.
  • Fee Descriptors within Monthly Merchant Statements are now displayed in their long form instead of the previous short form in order to more clearly describe card fee programs processed through your account.

Bug Fixes

  • Fixed a bug within the Merchant Tools interface that caused the province “Québec” to be displayed incorrectly due to the accent aigu on the letter 'e'.
  • Fixed a bug that caused the "Forgot your Password" feature within the Login screen to fail.
  • Fixed a bug that prevented the Merchant Statements .PDF documents from downloading.
  • Fixed a bug within Charge Details screens that prevented the correct calculation of the sum of charge items when one of the charge items included a negative dollar amount.
February 15, 2017 - Build 2.1.8

New Features

  • Merchants may now specify an Immediate Charge request (RBC99) as recurring using the Account Manager API. This is useful for merchants that have entered an agreement to charge their customers on a recurring basis, but the amounts that their customers are charged vary from month to month.
  • Merchants may now immediately authorize a card on file for a charge without also immediately capturing the amount authorized by setting the ProcessType value to “P” and selecting the interval Immediately (if using the online Merchant Tools) or initiating the ‘Perform Immediate Charge’ (RBC99) action (if using the Account Manager API).
  • Added the ability for merchants to input comments when refunding an order through the online Merchant Tools.

Improvements

  • The HTML Capture page now times out after 30 minutes, preventing merchants from failing to be notified of transactions processed by customers who have taken longer than 30 minutes to submit their payment.
  • Updated the Order Details page to allow merchants to view comments made while processing transactions via a Realtime API or the online Merchant Tools.
  • Updated the Order Details page to display comments merchants make regarding their orders.
  • Added a scroll bar to the Store Selector list of merchants with more than 15 stores.

Bug Fixes

  • Fixed a bug that prevented authorization requests destined to Rapid Connect to fail if they included a dash within the Postal Code.
  • Fixed a bug that prevented merchants from searching Invoices between two dates.
  • Fixed a bug that prevented merchants from searching the Settlement Details for transactions between two dates.
  • Fixed a bug that prevented merchants from searching their user logs for log entries between two dates.
  • Fixed a bug that prevented merchants from paying monthly PSiGate invoices online.
  • Fixed a bug that caused the default date range to not be applied to ‘Filter’ searches, causing those searches to time out.
October 25, 2016 - Build 2.1.7

New Features

  • Added the ability for merchants to include split-funding instructions within “Register Charge” requests submitted through the Account Manager API.
  • Created a new Verification API that will allow merchants to retrieve the payment details of their orders to ensure their orders have not been tampered with.
October 5, 2016 - Build 2.1.6

New Features

  • Added a new order item report that includes the item information associated with each order. This report is exported in the CSV file format.

Improvements

  • For merchants whose acquirer is PSiGate, a unique ID is now passed to the processor which will allow us to easily identify transactions associated with a chargeback.
  • Updated the Geographical IP Fraud Dictionary used to determine the location of a customer’s device and prevent potential fraud.

Bug Fixes

  • Fixed a bug that prevented the Current Batch screen in Merchant Tools from displaying “DEBIT” as the card type for IOP refunds.
  • Fixed a bug that caused the export function to fail within the Customers screen of Merchant Tools.
August 15, 2016 - Build 2.1.4

Notes

On Monday August 15th, 2016, PSiGate deployed build version 2.1.4 of its Gateway. We are excited to make you aware of the following enhancements and bug fixes so that you may take advantage of them in order to move your business forward.

New Features

  • Merchants may now include Split-Funding instructions within Sale, Confirm, Forced Confirm and Forced PostAuth requests initiated from within the Create Order and Reserved screens of the online Merchant Tools UI.
  • Split-Funded transactions are now reported within Settlements and Statements screens.
  • MasterCard Debit cards are now supported for merchants, whose acquirer is PSiGate and who opt into the MasterCard Debit service.

Improvements & Bug Fixes

  • Removed the “OrderID” and “Phone” fields from the list of fields that return the PSI-0127 error if the value of the field is found to possibly be a valid credit card number.
  • Fixed a bug that caused the PSi3D service to incorrectly return an ECI value of ‘7’ for MC transactions.
  • Removed the Recurring engine’s reliance on certain Realtime services thereby reducing the occurrence of PSI-0004 errors.
  • Fixed a bug that caused automatic Void transactions initiated as a result of a failed AVS/CVV check to return an incorrect response.
July 20, 2016 - Build 2.1.3

New Features

  • Added the ability for merchants to include split-funding instructions with their Sale or Confirmation requests through the Realtime XML or HTML APIs. When these transactions are funded, it is possible for more than one store to receive funds according to their split-funding instructions. The split-funding instructions can be viewed within the Order Details of the Merchant Tools interface.
  • This functionality will also be available through the Merchant Tools UI in upcoming releases.

Improvements & Bug Fixes

  • Improved error handling of our authorization processing engine, which will reduce delays in settlement process.
  • Fixed a bug that prevented the Refund button from appearing within the Confirmed Orders page of the Merchant Tools interface.

Security Improvements

    • As part of our continued effort to provide our merchants with secure payment gateway solutions and web applications, we have updated the list of card numbers that can be submitted within our Staging environments. The list of acceptable card numbers are listed below:

 

      • VISA Test Numbers:
        • 4111111111111111
        • 4012000033330026
        • 4111111111111112
        • 4012000033330036
        • 4005550000000019
        • 4387751111111111
        • 4387752222222227
        • 4005519255555555
        • 4116110000000018

 

      • VISA Debit Test Numbers:
        • 4005550000000001 + TestResult = "A"

 

      • MC Test Numbers:
        • 5454545454545454
        • 5424180279791732
        • 5191230005263745
        • 5442982222222220
        • 5405070000000011
        • 5529040000000015

 

      • Discover MC Test Numbers:
        • 6011000991300009

 

      • AMEX Test Numbers:
        • 371449635398431

 

June 20, 2016 - Build 2.1.2

New Features

  • Added the ability to support merchants who process Visa Debit card transactions, but do not process Credit card transactions.

Improvements & Bug Fixes

  • Enhanced the search and pagination of the Orders page.
  • Improved error messaging feedback to users in the Invoice Details page, so that it is clearer to users why an invoice was approved or declined.
  • Improved error messaging feedback to users in the All Transactions and Declined pages so that users may view the PSiGate error codes and error messages within the Result Code field.
  • Added column headings to the Transaction History section of the Order Details page.
  • Fixed a bug that caused intermittent errors to be returned when merchants sent multiple Immediate Charge requests (RBC99) sent through the Account Manager API.
  • Fixed the Search button within the ISO Merchant Selection page so that its display and function is consistent with other Search buttons within the Merchant Tools interface.
  • Fixed a bug that prevented certain merchants from being able to void transactions.
  • Fixed a bug that prevented sorting of the CustomerID field within the Customers page.
  • Fixed a bug that prevented all transaction records within the Current Settlement batch page from displaying when the default records per page was set to a value less than 500.
  • Fixed a bug that prevented the export of more than 1000 transaction/order records.
  • Fixed a bug that prevented users from submitting orders that included only one decimal place within the Item Price field of the Create Order page.
  • Fixed a bug that prevented saving HTML script containing image sources within the HTML Capture Settings.

Security Improvements

  • As part of our continued effort to provide our merchants with secure payment gateway solutions and web applications, we have added input field validation for cardholder data to the following applications: Real-time HTML API, Real-time HTML API, and the Account Manager XML API.
  • Input field validation also ensures that PSiGate provides a secure platform that is compliant with PCI DSS v3.1. Furthermore, it will help merchants reduce fraud by making sure that credit card data is always secure throughout the payment transaction.
  • Therefore, as of this release notification, PSiGate will no longer allow merchants to pass data that can be deemed as cardholder data in non-credit card fields. Merchants may be required to update their systems in order to prevent cardholder data from being sent to PSiGate in the following fields:
    • Real-time XML and HTML API:
      • OrderID
      • UserID
      • Bname
      • Bcompany
      • Baddress1
      • Baddress2
      • Bcity
      • Bprovince
      • Bcountry
      • Bpostalcode
      • Sname
      • Scompany
      • Saddress1
      • Saddress2
      • Scity
      • Sprovince
      • Scountry
      • Spostalcode
      • Phone
      • Fax
      • Email
      • Comments
      • Items
      • ItemID
      • ItemDescription
      • ESDFile
      • Options (Option Name, Option Value)
    • Merchant Tools:
      • Email Notifications:
        • E-mail Address fields (soon to be expired cards, soon to be expired charges and Overdue invoices)
      • General Settings:
        • Company Name, Store Name, Description, Address, City, Province, Country, Postal Code, Phone, Fax, Email, Website, Allowed IPs
      • Email Settings:
        • MerchantToEmail, MecrhantFromEmail, Receipt FromEmail
      • Credit Card Fraud Settings:
        • Send Email To
      • HTML Capture Settings:
        • StoreKey, DBA Display Name, Allowed Referring URLs, Default Approved URL, Default Decline URL, Allowed Approved URLs, Allowed Declined URLs
      • Create Order:
        • all fields in XML API
      • Create Customer:
        • Customer ID, Name, Company, Address1, Address2, City, Postal Code, Email, Phone, Tax
      • Create Charge Template
        • Template ID, Name
        • Use Items (Item ID, Description)
      • Customers > Actions > Add a Charge
        • Charge ID, Description
        • Use Items (Item ID, Description)
      • Customers > Actions > Add a Charge from Template
        • Charge ID
      • Customers > Actions > Add a Card
        • Card Holder Name
    • Account Management:
      • Recurring Billing (Action Code: RBCxx)
        • Affected XML Elements: RBCID, RBName, RBTrigger, ItemInfo->ProductID, ItemInfo->Description
      • RB Template (Action Code: CTLxx)
        • Affected XML Elements: RBCID, RBName, RBTrigger, ItemInfo->ProductID, ItemInfo->Description
      • Email Report (Action Code: EMRxx)
        • Affected XML Elements: *Address*
      • Invoice (Action Code: INVxx)
        • Affected XML Elements: *PayerName*
      • Account (Action Code: AMAxx)
        • Affected Common XML Elements: AccountID, Name, Company, Address1, Address2, City, Province, Postalcode, Country, Phone, Fax, Email, Comments, CardInfo->CardHoder
May 30, 2016 - Build 2.1.1

Notes

On Monday, May 30th, 2016, we released a few updates which refined a few features that were already available within Merchant Tools 2.0.

This deployment, however, appears to have caused some issues with the correct display of data within the platform, along with some other problems.

Before working with the Merchant Tools, please log in to your account and refresh your browser to resolve the data display issues.

If you continue to experience issues after refreshing your browser while logged into Merchant Tools, please clear your browser’s cache and cookie files and this should resolve the problem.

New Features

  • [GW-297] – Added the ability to accept cards within the MasterCard 2 BIN range.
  • [GW-147] – Added the ability to create recurring charges that when triggered will pre-authorize credit cards.
  • [GW-159] – Added the ability for merchants to send PreAuth requests with no dollar amount to verify credit cards and retrieve the result of AVS/CVV checks.
  • [MT-408] – Added the Settlement Summary information to the Settlement Details export file
  • [MT-219] – Added the Customer Name field to All Transactions and Reserved pages and their respective export files.
  • [MT-467] – Added the Currency field to Gateway Billing invoice details.

Improvements & Bug Fixes

  • [MT-454] – Enhanced the Search and Pagination features within the Customers page.
  • [MT-456] – Enhanced the Search and Pagination features within the All Transactions page.
  • [MT-457] – Enhanced the pagination feature within the Settlement and Statement Details pages.
  • [MT-361] – Fixed a bug that caused Settlements data to be incorrect for periods greater than nine months.
  • [MT-444] – Fixed a bug that caused the OrderIDs of some orders to be missing within the Funding Statements page of Merchant Tools.
  • [MT-445] – Fixed a bug that caused all charge items to be deleted when deleting X charge items.
  • [MT-463] – Fixed a bug that caused the bulk actions to not be displayed within the View Current Batch page.
  • [MT-466] – Fixed a bug that prevented users from finding customer records that included ampersands in the Customer ID field.
  • [MT-470] – Increased the number of rows displayed within the Gateway Billing page.
  • [MT-473] – Enhanced password security measures to prevent merchants from reusing the four most recent passwords.
  • [GW-204] – Fixed a bug that caused MC credit cards with the BIN 542418 to show up as Visa Debit instead of MC.
  • [GW-294] – Added code to prevent double-clicks from triggering duplicate immediate charges.
  • [GW-293] – Fixed a bug that caused the Merchant Tools to incorrectly display the data of IOP refunds.
  • [GW-301] – Fixed a bug that prevented IOP Merchants from being able to process refunds through the Merchant Tools.
February 19, 2016 - Build 2.0.0.8

Notes

On Friday, February 19th, 2016, PSiGate deployed build version 2.0.0.8 of its Gateway. We are excited to make you aware of the following enhancements and bug fixes so that you may take advantage of them in order to move your business forward.

Enhancements

  • Merchants may now pay their PSiGate invoices through the Gateway Billing page in the Statements tab.
  • Merchants may now refund Interac Online orders through the Order Details or Confirmed screens within the Orders section of the online Merchant Tools interface.
  • Merchants may now specify the Process Type of a Charge within the Create Charge or Create Charge Template screens.

Process Types

  • Automatic Sale (Default) – Authorize the card associated with an invoice when the invoice is generated and Capture those funds immediately.
  • Automatic Auth – Authorize the card associated with an invoice when the invoice is generated.
  • Manual Sale – Generate an invoice, but do not attempt to authorize the card.
  • Installment – Divide the charge amount into X invoices and schedule each invoice to generate according to a specified interval
    An updated and more accurate set of AVS (Address Verification Service) response code descriptions.
  • Merchants with special permissions may now refund orders without referencing a previously confirmed order through our XML API and a button labeled “Credit Customer” within the Orders screen.

Bug Fixes

  • Fixed the bug that caused the message “proxy error” to display and prevented users from interacting further with the Merchant Tools until they refreshed their browser.
  • Fixed a bug that prevented merchants, whose stores were set to Read Only, from viewing their store’s data.
  • Fixed a bug that caused some merchants who sent an Interac Online test transaction to be directed to an incorrect response page.
  • Fixed a bug that prevented Interac Online transaction records from appearing within the Settlement Details screen and export file.