Release 3.2.1

Modified on Tue, 1 Apr at 9:19 PM

The Release was performed on 04/01/2025 at 06:00 PM.



  • For merchants in the auto industry, advisor users will now receive a "New Payment Received" email notification when a payment is completed for an existing order via the single payment page.

  • A consistent and professional brand image is essential for building trust and recognition with your clients. Strictly’s platform makes it easy to set up and customize your branding. We’ve added more customization options, giving you greater flexibility and control over the guest-facing elements your users see in emails and on the single payment page. To learn more, check out this article. More changes, including preview functionality, are coming soon.  

  • Your emails are getting a new look! We’ve started enhancing the emails you send to your clients. They now feature a more modern design, including headlines, a consistent message, and additional information in the footer. Stay tuned—soon, you’ll also have the option to customize your email's copy and subject line. You can control your email look in your ‘Branding” section. To learn more, check out this article.  

  • As part of our ongoing commitment to security and performance, this release introduces behind-the-scenes improvements aligned with PCI and industry best practices. We’ve also upgraded core components of our platform to ensure even greater reliability and speed for our users.

  • We’re excited to announce that new integrations are available through our marketplace! These applications enhance merchant workflows by seamlessly connecting their Practice Management Systems (PMS) with Strictly’s payment processing.

  • We have made several technical and usability improvements. These enhancements have been carefully designed and tested to improve our platform's overall performance, reliability, and user experience.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article