Release Date: September 28, 2023
This release delivers a custom reconciliation report for a client.
| Ticket | Type | Description |
|---|---|---|
| CPAY-4472 | Feature | Custom work. Set up a custom daily reconciliation report for a client. The report runs automatically and generates a BAI2 format file. |
Release Date: September 26, 2023
This release fixes an issue where some transactions didn't sync correctly.
| Ticket | Type | Description |
|---|---|---|
| CPAY-5035 | Fix | In some cases, posted transactions weren't synced and still showed as unposted in REPAY Payables. Now, the status is synced and the posting date is shown. |
Release Date: September 26, 2023
This release updates all supported versions of Sage 300. It includes usability updates to REPAY batch processing, improved messaging for credit card errors, and installers for all versions of Sage 300. It also adds support for a second payment gateway. The new gateway is referred to as the REPAY gateway; our existing gateway is now referred to as the Legacy gateway. For more information, see REPAY Gateway Notes, later in this release note.
| Ticket | Type | Description |
|---|---|---|
| ERP-732 | Feature | Branding update. All references to APS, APSPays, and APS Payments are now REPAY. |
| Multiple | Feature | REPAY Gateway. Updated and tested all REPAY payment and reconciliation features to ensure compatibility with both REPAY and Legacy gateways. |
| ERP-1109, ERP-1110 | Feature | The REPAY Setup window has been reorganized and tabs added to the bottom to allow setting up either the REPAY Gateway or Legacy Gateway. (The REPAY Credentials section has been moved to the Legacy Gateway tab.) Click the corresponding tab, set Active to Yes, and enter the credentials:
 |
| Multiple | Feature | Improved error messaging lets you know when the connection to the payment gateway fails and the payment can't be processed. Communication errors are caused by incorrect credentials on the REPAY Setup. Improved errors were added to:
|
| ERP-1992, ERP-1993 | Feature | The Sage 300 customer ID and contact email are now sent as part of the transaction details and are visible in the payment gateway. |
| ERP-2298 | Feature | REPAY Batch Processing. In the search criteria, the Document Type filter "Invoice" is now labeled Shipment. |
| ERP-3334 | Fix | You couldn't add or update a credit card if the billing address was in Canada. REPAY incorrectly prompted for a 5-digit (US) Zip Code. Now it accepts 5-6 alphanumeric characters. |
| ERP-3636, ERP-3737 | Fix | REPAY Batch Processing. Updated the Card Not Registered error message to explain that an order couldn't be processed because the customer record didn't have a credit card associated with it. |
| ERP-4257 | Feature | When Ops Inquiry is enabled in Sage 300, the Ops Inquiry button is accessible on the REPAY Order Entry screen. |
| Sage 300 2018 | Sage 300 2019 | Sage 300 2020 | Sage 300 2021 |
|---|---|---|---|
| REPAY v6.5.60 | REPAY v6.6.60 | REPAY v6.7.60 | REPAY v6.8.60 |
Note: For Sage 300 2022 and 2023, be sure to download the version that corresponds to the Product Update your system is running.
| Sage 300 2022 | Sage 300 2023 |
|---|---|
| 2022.0 - REPAY v6.9.60 PU1 - REPAY v6.9.61 PU2 - REPAY v6.9.62 PU3 - REPAY v6.9.63 PU4 - REPAY v6.9.64 | 2023.0 - REPAY v7.0.60 PU1 - REPAY v7.0.61 |
There is no change for current REPAY Sage 300 customers. Continue to use your existing payment setup. (If you previously sent transactions using the Legacy gateway, you can't change to the new REPAY gateway.)
If you are a new customer, work with your implementation team to select the gateway that is appropriate for your needs. The REPAY gateway doesn't currently support EMV transactions.
Release Date: September 20, 2023
This hotfix corrects a deployment issue in version 292 that caused some ACH transactions to fail.
Release Date: September 18, 2023
This release allows imported payments to be grouped by payment number (instead of by vendor), includes updates for CDK Global, implements the REPAY data retention policy of 36 months, and fixes a login error that affected some internal REPAY users. It also includes prep work for a new enhanced ACH feature.
| Ticket | Type | Description |
|---|---|---|
| CPAY-3643, CPAY-3930 | Feature | Customers who import payments to REPAY Payables using SFTP can opt to have them grouped by payment number instead of vendor. Payments to the same vendor will stay separate rather than be grouped into one payment per vendor. Reconciliation files will list all payments sent by the customer so they can be cleared. Admins: To enable this feature, in Customer Setup > Configure Workflows section, select Group By Payment Number.  |
| CPAY-4046 | Feature | CDK Global. Setup > Customer Setup. The new Look Back Days option lets administrators set the number of days back to import open AP invoices from CDK to 30, 60, 90, or 120 days. The default is 90 days back. The maximum number of look-ahead days is 14 (retrieve invoices with a due date up to 14 days in the future). This option is available when the integration is set to CDK. |
| CPAY-4106 | Feature | Data retention. REPAY Payables API. All queries return data for the previous 36 months; data older than 36 months is filtered out. |
| CPAY-4108 | Feature | Data retention. In REPAY Payables, all searches and reports are limited to the previous 36 months. |
| CPAY-4344 | Feature | Internal. Development work to accommodate additional date/time formats in virtual card transactions. |
| CPAY-4345 | Fix | The status of virtual card transactions that cleared after five days wasn't updated completely. Now they show as settled. |
| CPAY-4585 | Fix | Internal. Multi-factor authentication. Fixed an Okta login issue that affected certain REPAY internal users. |
| CPAY-4642 | Feature | CDK Global. REPAY now retrieves invoices to be paid by company ID, ensuring that only invoices for a specific customer are retrieved. This addresses a scenario where when a customer shares a dealer ID with another customer, it is possible to retrieve the wrong invoices. |
| Multiple | Feature | Internal security fixes and updates to third-party libraries. |
Release Date: September 15, 2023
REPAY for Acumatica is now certified for Acumatica versions 2022 R2, 2023 R1, and 2023 R2. This release includes support for EMV prepayments, updates to surcharge handling, and troubleshooting improvements.
Acumatica Versions: 2021 R2, 2022 R1, 2022 R2, 2023 R1, 2023 R2
| Ticket | Type | Description |
|---|---|---|
| ERP-3065 | Feature | Internal. Refactored code for importing settlement batches to meet 2022 R2 certification requirements. |
| ERP-3175, ERP-4143 | Feature | To assist in troubleshooting, the REPAY customization version is now sent to the payment gateway with each transaction. The REPAY version is captured in Merchant Defined Field 2. |
| ERP-3341 | Feature | Internal. Updated the ClickToPay customization project to support recent API changes. |
| Multiple | Feature | The REPAY integration is certified for Acumatica versions 2022 R2, 2023 R1, and 2023 R2. |
| ERP-4037 | Feature | Payments and Applications. When a surcharge is paid, the ClickToPay surcharge invoice is now included on the Application History tab. |
| ERP-4205, ERP-4206 | Fix | Performed an internal review and ensured that custom controls within the REPAY integration have unique IDs. This addresses an installation issue reported by a customer. When they attempted to publish version 23.0607.0 of the base customization it failed with errors like:The ID xxxx is already used by another control. |
| ERP-4275 | Feature | Prepayments are now supported for EMV device payment methods. |
| ERP-4774 | Fix | Acumatica 2023 R1. Checks and Payments. When you voided a check that was paid using the REPAY AP integration, the payment wasn't updated correctly. Now, the payment and payment group (if this is the only payment in the group) are cancelled on the payment gateway and its status is updated in Acumatica. |
IMPORTANT: To avoid conflicts with other modifications or customization projects, we strongly advise that you install and test REPAY Base and ClickToPay customization projects in a staging or sandbox environment before deploying them to production. If you run into issues, please contact Support.
| Base Customization Projects | 2022 R1 | 2022 R2 | 2023 R1 | 2023 R2 |
| ClickToPay Customization Projects | 2022 R1 | 2022 R2 | 2023 R1 | 2023 R2 |
Release Date: September 13, 2023
This release includes fixes for a missing Level III validation error message (API), security vulnerabilities, and a UI issue that allowed admins to submit a manual payment multiple times.
It also includes updates to user management and tracking (for REPAY admins) and preparations for the rollout of multi-factor authentication (MFA) to REPAY ClickToPay. These changes don't impact customers.
| Ticket | Type | Description |
|---|---|---|
| ERP-2636 | Fix | ClickToPay API. When posting an invoice, if the product array was empty, Level III validation errors were returned as a generic message: An unspecified system error has occurred. Now, the following error message is returned.For Level III transactions, at least one product must be included. |
| ERP-3578 | Feature | Multi-factor authentication. In the future, users with the REPAY Admin role will sign in at /Administration/Login instead of /Account/Login. |
| ERP-3743 | Feature | Internal. Manage Users. Removed the REPAY Employee role. The following roles are active:
|
| ERP-4026 | Feature | Internal. Reporting > User Reporting. You can export the login tracking report to a CSV file. |
| ERP-4615, ERP-4616 | Feature | Multi-factor authentication. Set up test and production environments. |
| ERP-4659 | Fix | Internal security fixes and security upgrades to third-party libraries. |
| ERP-4909 | Fix | Internal. Merchant Portal. When making a manual payment on an invoice or order, you could click Pay Now more than once and accidentally submit multiple payments for the same amount. |
Release Date: September 11, 2023
This is an internal release for CDK Global; it adjusts how invoices to be paid are retrieved. These invoices are available to CDK users as payment groups in REPAY Payables.
| Ticket | Type | Description |
|---|---|---|
| CPAY-3916 | Feature | CDK Global. Internal. Invoices to be paid are now filtered by company ID, ensuring that only invoices for a specific customer are retrieved. Previously, invoices were retrieved using the dealer ID. |
| CPAY-3988 | Feature | CDK Global. Internal setup work to manage the date range of invoices to pay retrieved by REPAY Payables. |
Release Date: September 8, 2023
This release fixes credit card validation errors and errors that prevented adding a payment on account.
| Ticket | Type | Description |
|---|---|---|
| ERP-4738 | Fix | Business Partner Master Data > Repay tab. You couldn't add a new payment method to a customer because the Country and State/Province fields weren't pulled in from the addresses and you couldn't edit these fields on the Card Details window. In addition, the CVV value entered wasn't saved. |
| ERP-4845 | Fix | Incoming Payments. System errors prevented recording a payment on account. When you created an incoming payment and entered a "payment on account" amount, the following error was displayed. $-x.xx of the amount to be paid is not matched to an existing invoice. Do you want to post the payment as payment on account?Clicking Yes to apply the payment displayed a second error. You couldn't proceed.Cannot add payment with no document and no "payment on account" amount |
The installer is compatible with SAP Business One for Microsoft SQL and SAP HANA.
Download the REPAY add-on (Zip file includes x86 and x64 installers)
| Documentation | Portals & Pages | Product Demos |
|---|---|---|
| SAP B1 User Guide (June 2024) | REPAY Status Page | SAP B1 Card & ACH |
| REPAY Gateway Login | REPAY ClickToPay | |
| REPAY Elevate | ||
| REPAY Payables Platform |
Release Date: September 6, 2023
This release fixes a UI issue that allowed buyers to submit multiple payments for one invoice.
It also implements the REPAY policy for the retention of customer and payment data. Under this policy, invoices, sales orders, customers, and payment data will be accessible for a rolling period of 36 months past the creation date.
Data older than seven years (84 months) has been deleted from REPAY systems and data between 36 and 84 months has been removed from production systems and archived.
| Ticket | Type | Description |
|---|---|---|
| ERP-4880 | Fix | When paying an invoice, you could click Complete Payment more than once and accidentally submit multiple payments for the same amount. |
| ERP-4523 | Feature | Invoices, sales orders, and payment token data that are older than seven years have been deleted from all REPAY systems. |
| ERP-4524 | Feature | ClickToPay API. Queries of invoices, orders, and payment data return data for the previous 36 months. |
| ERP-4526, ERP-4527 | Feature | The ClickToPay payment portal only displays invoices and orders that have been updated in the previous 36 months. |
| ERP-4674, ERP-4675, ERP-4676, ERP-4677 | Feature | The following reports are limited to the previous 36 months:
|
| ERP-4766 | Feature | ClickToPay API. The customer query returns active customers for the previous 36 months (customers with an invoice posted for them during that period). If an invoice is posted to a customer after 36 months of inactivity, they will be created as a new customer with a new REPAY Vault ID and address. |