Released: March 28, 2025

This release sends Level 3 data to the payment gateway, fixes an issue with broken ClickToPay links in Paperless Office print/emails, and defaults to the Legacy gateway for importing credit card tokens.

Release Notes

Downloads

• Sage 100 2024 (PU 0-1)
• Sage 100 2023 (PU 0-4)
• Sage 100 2022 (PU 0-6)

Resources

Released: January 7, 2025

This release adds the check number from REPAY Payables to the Payment History Inquiry screen (Payables).

Release Notes

Ticket	Type	Description
ERP-7713	Feature	Payables. On the Payment History Inquiry screen, the Repay Vendor Payments section now includes the check number for payments that were issued as checks.

Downloads

• Sage 100 2024 (PU 0-1)
• Sage 100 2023 (PU 0-4)
• Sage 100 2022 (PU 0-6)

Resources

Released: December 5, 2024

This release adds the discount due date to the invoice approval screen, adds support for Sage 100 2024 PU1 and addresses several bugs.

Release Notes

You must enter payment information in the following fields in order to accept the transaction.

Downloads

• Sage 100 2024 (PU 0-1)
• Sage 100 2023 (PU 0-3)
• Sage 100 2022 (PU 0-6)

Resources

Posted: October 29, 2024

As part of our commitment to maintaining the highest security standards, at the end of January 2025, we're updating the cipher suites used with the REPAY ClickToPay hosted credit card form in Sage 100. With the change, the TLS 1.2 cipher suite TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA will no longer be supported. This change is crucial for ensuring the continued security of our services and compliance with industry standards.

Important: After January 31, 2025, connections using unsupported ciphers will be refused, potentially disrupting your service.

Please review this announcement for supported cipher suites, instructions for testing your connection and related documentation. 

Action Required before January 31, 2025

1. Review your current Sage 100 server operating system, cipher suite usage and official Sage supported versions.
2. Update your operating system to use one of the supported cipher suites listed below.
3. Test your connection to ensure everything is working correctly. Instructions are included later in this note.

Supported Cipher Suites

TLS 1.3
TLS_AES_128_GCM_SHA256
TLS_AES_256_GCM_SHA384
TLS_CHACHA20_POLY1305_SHA256

TLS 1.2

ECDHE-ECDSA-AES128-GCM-SHA256
ECDHE-RSA-AES128-GCM-SHA256
ECDHE-ECDSA-AES256-GCM-SHA384
ECDHE-RSA-AES256-GCM-SHA384
ECDHE-ECDSA-CHACHA20-POLY1305
ECDHE-RSA-CHACHA20-POLY1305
DHE_RSA_WITH_CHACHA20_POLY1305_SHA256

Test Your Connection

Here's a quick way to confirm whether the change will impact your Sage 100 ERP system:

On the Sage 100 server, open Internet Explorer 11 and navigate to the following URL: https://testportal.apsclicktopay.com. If it loads without error, your system will not be impacted. No action is necessary.

Test Your Connection in Sandbox (for IT and Sage Admins)

The ClickToPay sandbox environment is configured to only support the listed ciphers. To ensure your system supports these ciphers, in Sage 100 modify the ClickToPay URLs and point them to the sandbox environment.

To test connections:

1. In Sage 100, go to Library Master > URL Maintenance.
2. In the ClickToPay URLs, change:
   • portal.apsclicktopay.com to testportal.apsclicktopay.com
   • api.apsclicktopay.com to testapi.apsclicktopay.com
     
     
3. Now test the connection by adding a credit card to a customer.
   • Go to Accounts Receivable > Customer Maintenance and on the Additional tab click Credit Cards/ACH.
   • Select CC for the payment type and enter a payment ID. Click Add New. If the REPAY credit card form opens, your network connection is using a supported cipher suite.  
   • Click Cancel. Remember to change the ClickToPay URLs back to production.

ClickToPay URLs in Sage 100

https://portal.apsclicktopay.com/EasyPay
https://portal.apsclicktopay.com/EPay/Payments
https://api.apsclicktopay.com
https://portal.apsclicktopay.com/Invoices/ClickToPay
https://portal.apsclicktopay.com/order/pay
https://portal.apsclicktopay.com/Invoices/CustomerLink

Related Documentation

• REPAY for Sage 100 Release Notes
• Sage 100 Supported Versions (Sage)
• Windows Server 2012 and 2012 R2 reaching end of support (Microsoft)
• Lifecycle FAQ - Internet Explorer 11 End of Life (Microsoft)

Updated: October 14, 2024
Released: October 8, 2024

Applies to Sage 100 implementations with SQL databases. A recent gateway update increased the transaction ID length, causing "Transaction not found REFID" errors when attempting to capture pre-authorizations. This release increases the transaction ID max length from 10 to 15 digits, accommodating longer transaction IDs returned by the legacy and REPAY payment gateways.

For instructions on resolving payment captures that failed, see Fix for "Transaction not found REFID" error when capturing payments.

Release Notes

Downloads

• Sage 100 2017 (PU 0-6)
• Sage 100 2018 (PU 0-10)
• Sage 100 2019 (PU 0-4)
• Sage 100 2020 (PU 0-5)
• Sage 100 2021 (PU 0-6)
• Sage 100 2022 (PU 0-6)
• Sage 100 2023 (PU 0-4)
• Sage 100 2024 (PU 0-1)

Resources

Posted: October 10, 2024

Affects Sage 100 implementations with SQL databases. Flat file storage isn't affected.

Recently, transaction IDs from the payment gateway increased to 11 digits. By default, Sage 100 supports 10-digit transaction IDs. Pre-authorizations were still successful, but only the first 10 digits of the transaction ID were stored in Sage 100. Running the Daily Sales Reports/Update process to capture pre-authorizations resulted in Transaction not found REFID errors like the following example.

Version 7.09 of the REPAY addition increases the field length to 15 digits and ensures that all future transactions will be supported.

Resolving Payment Captures That Failed

1. Update to the REPAY addition version 7.09. REPAY installers are available from the Sage 100 7.09 Release Notes.
2. Sign in to the payment gateway and run a report to retrieve the transactions with the error. Download the report. The first column of the report contains the transaction ID.
3. In Sage 100, fix incomplete transaction IDs:
   • Go to Library Master > Utilities > Data File and Display Maintenance and open the Sales Order (so_salesorderpayment) or Sales Invoice (so_salesinvoicepayment) payment table (as applicable).
   • Browse or search the records and locate the sales invoice or sales order to update. Click Edit.
   • Copy the transaction ID you downloaded from the payment gateway and paste it in the CreditCardTransactionID$ field. Click Update to save changes.
   • Repeat this step to fix other payments.
4. Re-run the Daily Sales Reports/Update to resolve payment captures that previously failed due to the error. 
   • Go to Sales Order > Daily Sales Reports/Updates and select Perform Payment Processing. 
   • Click Print to process payments.

For detailed instructions with screenshots, see Sage100 7.09: How to fix "Transaction Not Found REFID" error.

Resources

Posted: October 3, 2024

Users of 64-bit versions of Sage 100 might encounter issues with the REPAY credit card form that allows them to take a customer's payment. To address this issue, set the browser emulation by adding a new DWORD value defined as "pvxwin64.exe"=dword:00002af8 to this registry location:

HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl\ FEATURE_BROWSER_EMULATION

To update a user's workstation:

1. Use Windows search and open the Registry Editor (search for regedit or Registry).
   
   
2. Navigate to HKEY_CURRENT_USER > Software > Microsoft > Internet Explorer > Main > FeatureControl > FEATURE_BROWSER_EMULATION.
   
   Tip: at the top of the Registry next to Computer, type or paste \HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION
   
   
3. In the right panel, right-click and select New > DWORD (32-bit) Value and name the new entry pvxwin64.exe.
   
   
4. Double-click the new entry to edit it, and enter 2af8 for the value data and base Hexadecimal. Click OK to save changes.
   
   
   The new entry is listed.

   

Resources

Released: August 7, 2024

This release includes improvements to the Sage Intacct Payables integration, fixes an issue with partial payments in Intacct, and corrects how the REPAY Vault Entry screen defaults the name on the account for customer ACH payment methods (used by Acumatica and Sage 100). It also includes internal security fixes.

Release Notes

Ticket	Type	Description
ERP-6809, ERP-6948	Feature	Sage Intacct. To assist with reporting, additional payment details are captured for posted payments and available in Intacct. Go to REPAY > REPAY Payables Payments to view the following information: REPAY payment number, payment group name and status Payment type - ACH, check or virtual card Check number and image URL - for checks Last 4 digits of card - for virtual cards
ERP-7078	Feature	Sage Intacct. REPAY > REPAY AP Payment Groups. Improved syncing removes any orphaned, errored or duplicate payment groups from the list.
ERP-4266	Fix	REPAY Vault Entry (also referred to as the hosted form) used by Acumatica and Sage 100. When vaulting (saving) an ACH payment method for a customer, the Repay Vault Entry screen now correctly defaults the name on the account ("name on check") to: First and last name of the billing contact for Personal accounts (if available) Account name for Business accounts
ERP-6929, ERP-6964	Fix	Sage Intacct. Accounts Payable > Pay Bills. Partial payments were recorded correctly in Intacct, but the full amount due was sent to REPAY Payables as the payment.
Multiple	Fix	Internal security fixes and updates.

Resources

Released: August 6, 2024

This release adds support for Sage 100 2024.1 and Sage 100 2023.4. It also optimizes how the REPAY integration connects to the legacy payment gateway and fixes two bugs.

Release Notes

Downloads

• Sage 100 2022 (PU 0-6)
• Sage 100 2023 (PU 0-4)
• Sage 100 2024 (PU 0-1)

Resources

Released: May 31, 2024

This release adds support for Sage 100 2024 and the latest product updates (PU) to Sage 100 2022 and 2023.

Downloads

• Sage 100 2024 (Base)
• Sage 100 2023 (PU 0-3)
• Sage 100 2022 (PU 0-6)

For earlier versions of Sage 100, go to Software Downloads.

Resources