Released: November 13, 2024
This release includes internal security improvements, work to add a new check printing provider and support for Canadian vendor payments (Canadian companies paying vendors in CA$). There are no customer-facing changes.
| Ticket | Type | Description |
|---|---|---|
| Multiple | Feature | Development work to add a new check printing provider. |
| Multiple | Fix | Internal security fixes and updates. |
Released: November 11, 2024
This release provides an installer compatible with Sage 300 2023 PU3. For the latest version of all installers, go to Software Downloads.
Sage 300 2023
Released: November 4, 2024
This release lets you use the ClickToPay API to retrieve the QR code for a sales order and removes the change password link from the My Account page. (With the introduction of MFA, users should either click Forgot password on the login screen or use their employer's change password function to update their passwords.)
| Ticket | Type | Description |
|---|---|---|
| ERP-7345 | Feature | ClickToPay API. You can create a QR code when adding or updating a sales order and query a sales order and retrieve its QR code. Use the so/create, so/update and so/query requests and set the qrCode parameter to true. The QR code is returned in the response as a Base64-encoded string. QR codes are visible on the ClickToPay payments portal, allowing buyers to open and pay invoices and sales orders on their mobile devices. |
| ERP-6800 | Fix | Internal security fix. |
| ERP-7546 | Fix | My Account. We removed the change password link from the My Account page (accessed by clicking your email address in top right when signed in). If you sign in using:
 |
| 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 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 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. |