Sage Software; Paya Virtual Terminal
This document explains new features added to Sage 50 2017 US Edition that impact integrations with the Paya Gateway (this assumes knowledge of existing workflows in Sage 50).
Sage 50 2017 has added two new features that impact how processing works with your Paya account.
1. Sage 50 2017 now integrates with Sage Exchange Desktop 2.0.
2. Sage 50 2017 now supports Enterprise ACH processing directly in the application.
Sage Exchange Desktop 2.0
During the upgrade process, a Merchant with existing credit card processing should receive a prompt about uninstalling Sage Exchange Desktop 1.0. They should allow this to occur. Part of this process is to install Sage Exchange Desktop 2.0. This is required for the merchant to continue processing. There are no known issues that result from having SED1.0 and SED2.0 installed at the same time.
A new 'ACH Information' section has been added to the Payment and Credit tab in Sage 50. This allows the Merchant to store both a credit card number and bank account number. If they do not have the ACH Service enabled, the SED will default to the credit card vault window.
Just like in the previous version, the selected 'Payment Method' has no impact on the type of transaction being processed.
ACH Processing with Stored Information
If the Merchant has records stored for credit card and ACH, they will be given an opportunity to choose the stored record.
ACH Processing without Stored Information
If there is no stored record and the Merchant has the ACH Service on their account, they will be given an option to the payment type.
The originator class type is not stored in the software or vault. The Merchant will need to select the correct OID type each time. The drop-down list also includes all OID types regardless of them being enabled in the Virtual Terminal. Most Merchants will use pre-arranged Payment and Deposit Entry (PPE) for consumers or Cash Concentration or Disbursement (CCD) for businesses.