November 8th Release
Fixes:
- Fix issue with helcim customer search as API only returns 100 customers - undocumented. Now we send the drop down search term to filter on the api side.
New updates and improvements to Benji Pays
Fixes:
Improvements:
Fixes
Add a "test" button to send a test email to ensure SMTP settings are working when using an external SMTP server.
1
Fixes:
New Features
Fixes
We are launching our Beta of Halo PSA SSO. We will be starting with a small number of merchants while we test and gather feedback and will open this Beta up to more merchants soon.
Provide a way to have end customers log into the Benji Pays self serve customer portal either by using their Halo credentials against the Halo IDP, or via a custom integration that would allow Benji Pays to securely verify the user and log them into their Benji Pays portal.
7
Create a button in Benji Pays that automates the creation of a custom button on the client entity in Halo - this butt when clicked in Halo will open the customer's record in Benji Pays - the user must be logged into Benji pays already.
0
New
Fixes
New
Fixes:
Add ability to use hosted ConnectWise api url.
0
Limits unnecessary emails. Prevent the important information from being missed.
1
To increase security and reduce the chances of card testing we will add recaptcha to all payment pages that do not required a login. Default will be Googles invisible captcha that analyzes behaviour and requires user's input if it deems the session is riskyAn option to enhance recaptcha coverage will be available to all of our merchants to add the "I'm not a robot" checkbox recaptcha instead of the default invisible recaptcha.
0
Other:
Fixes:
Helcim API Updates
Required update of our Helcim integration to their new V2 API is complete. Existing Helcim configurations will continue to function, however we will be reaching out to merchants to assist them with migrating their configuration to the new API in August prior to Helcim retiring the old API.
Update to support helcim api V2.
0
Other updates:
New:
Aug 1, 2024 is the deadline Expiring access tokens coming to the US and Canada in October 2023 Starting October 2023, Clover is rolling out expiring access (authentication) tokens in the United States (US) and Canada. Use these short-lived, expiring access tokens to: Authenticate with Clover APIs Improve the security of your applications and merchants’ data Since expiring tokens are short-lived, your applications must manage the expiring access tokens and create refresh tokens to maintain continuous access to the APIs. IMPORTANT All apps in the United States and Canada must use expiring access tokens by August 1, 2024. Apps in the United States or Canada New applications—Clover requires that new apps use expiring access and refresh tokens. Existing (legacy) applications—If you have Clover apps, start migrating your apps to use expiring access and refresh tokens. For new and existing apps, you can roll out the expiring access tokens as you deem fit—for example, all at once or by using feature flags or gradual rollouts. See Authenticate with OAuth—Canada and US for more information.
0
The plan here is to bring the new payment modal concepts from our Self Serve customer portal into the main application, allowing for a single stop to select 1 or more invoices, enter the amounts (if not paying the full amounts) and add a new payment method all at once.
6