Released: October 31, 2024
This release provides an installer compatible with Sage 300 2023 PU2. For the latest version of all installers, go to Software Downloads.
Sage 300 2023
Released: October 30, 2024
This release enhances handling of payment import files and includes security fixes, additional logging and internal work to add a new check printing provider.
Note: In the coming months, we will begin migrating FTP users to a new, more secure SFTP system. Our Customer Service team will be reaching out with more details.
| Ticket | Type | Description |
|---|---|---|
| CPAY-9344 | Feature | Payment files on the new AWS SFTP server are now archived and cleared from the inbound folder after processing. |
| CPAY-9653, CPAY-9694 | Feature | Development work to add a new check printing provider. |
| Multiple | Fix | Internal security fixes and updates. |
Posted: October 28, 2024
Corrected: 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.
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
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.
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:
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
Released: October 25, 2024
This release provides an installer compatible with Sage 300 2023 PU1. For the latest version of all installers, go to Software Downloads.
Sage 300 2023
Released: October 21, 2024
This release fixes a minor UI issue on the ClickToPay payments portal.
| Ticket | Type | Description |
|---|---|---|
| ERP-7488 | Fix | Payments portal. Removed an empty "test" link from the page footer. |
| Documentation | Portals & Pages | Product Demos |
|---|---|---|
| REPAY for Sage Intacct User Guide | REPAY Payables Platform | Vendor Opt-In for Sage Intacct |
| REPAY Status Page | REPAY ClickToPay | |
| REPAY for Sage Intacct AR |
Released: October 18, 2024
This release adds support for using the Apply Entries workflow in Payment Journals to send posted purchase invoices to REPAY for payment.
| Ticket | Type | Description |
|---|---|---|
| ERP-7477 | Feature | Payment Journals. Use the Apply Entries workflow to select posted purchase invoices for a vendor, add them to a payment and send them to REPAY for payment. Follow the standard workflow:
Then:
|
| Documentation | Portals & Pages | Product Demos |
|---|---|---|
| REPAY for Dynamics 365 Business Central Guide | REPAY Status Page | Dynamics 365 AP Vendor Payments |
| REPAY Payables Platform |
Released: October 17, 2024
This release includes ongoing work to maintain and improve the security of the REPAY Payables infrastructure, services and data. There are no customer-facing changes.
| Ticket | Type | Description |
|---|---|---|
| Multiple | Fix | Internal security fixes and updates to third-party libraries. |
Released: October 16, 2024
This release lets you use the ClickToPay API to automatically email invoice receipts, displays the company name in the invoice receipt "from" address and adds usability improvements to the Sage Intacct AP integration.
| Ticket | Type | Description |
|---|---|---|
| ERP-7031 | Feature | ClickToPay API. You can automatically send the invoice receipt via email to the buyer's email address. Use the invoices/create or invoices/query requests and set the EmailReceipt parameter to true. The receipt will be sent to the customerEmail parameter in the invoice or fall back to the address saved with the customer record. |
| ERP-7312, ERP-7356 | Feature | Sage Intacct. Paging and filtering improvements to REPAY > REPAY AP Payment Groups. You can filter the list of payment groups by group name, customer ID and status (for approved groups). To improve navigation, 10 payment groups are displayed per page. |
| ERP-7355 | Feature | Sage Intacct. Bills > REPAY tab. If a payment fails, the new Error Message field displays error details. |
| ERP-7452 | Feature | Invoice receipts now include the client's company name in the from address. |
| Documentation | Portals & Pages | Product Demos |
|---|---|---|
| REPAY for Sage Intacct User Guide | REPAY Payables Platform | Vendor Opt-In for Sage Intacct |
| REPAY Status Page | REPAY ClickToPay | |
| REPAY for Sage Intacct AR |
Released: October 14, 2024
This release provides an installer compatible with Sage 300 2024 PU2. For the latest version of all installers, go to Software Downloads.
Sage 300 2024
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.
| Ticket | Type | Description |
|---|---|---|
| Multiple | Feature | Support for credit card transaction IDs up to 15 digits. The legacy payment gateway recently updated credit card transaction IDs to 11 digits. |