Status update


15 April 2021: There was a connectivity issue with Engaging Networks Toronto datacenter due to a DDOS attack that was causing slowness in the application. This was affecting client pages and the ability to login to your account. At this time we are back up and running with minimal slowness.

Our developers are working with our data center to monitor the situation closely.

Data staging jobs did not run for some clients

25 March 2021: We have had reports that the job to run daily exports for clients using the Bulk Export API did not run earlier today.  This only affects clients on the Toronto server (non-USA clients) using our automated export API. 

Recent software updates

We are continually adding new features to the software. The most recent release deployed February 2021. For further details on each of our updates, see the link to release notes in the related articles section on the right sidebar.

Important notices

3D Secure 2 and SCA

Those with supporters in the EU/UK should be mindful of upcoming Strong Customer Authentication (SCA) compliance deadlines for security measures (Dec. 31, 2020 for the EU and September 2021 for the UK). Additional updates will be shared soon on Peer-to-Peer updates, and all gateway statuses can be found here

Please note, PayPal 3D Secure is not currently accepting new clients in the existing implementation with Cardinal Commerce on Engaging Networks. An alternative solution is being identified, and please contact the Support team with any questions on your compliance status or SCA’s impact on your organization. 

Legacy software

The ability to edit and create legacy pages has been removed from the software. All pages should be created in the page-builder tools. Please Close any live pages. You can still view closed pages – click here for more. Legacy triggers are shut down. Please use marketing automations for that.

Payment gateway transaction ID

Following a Visa and MasterCard mandate for payment processors, we will now store an additional id for the transaction id. For clients using Worldpay, you will note a change in the gateway transaction ID (campaign data 2) in your Engaging Network’s Transactional Data, post this release. Worldpay transaction IDs moving forward will have 2 parts to them (paymentToken__networkTransactionId). The ‘3D Secure’ payment flow is now supported, through the PaySafe gateway. If you are interested in applying this for card processing feature, please reach out to support.

TLS 1.0 deprecation

Engaging Networks disabled TLS 1.0 on 1st June 2018. If you and your supporters are using modern browsers, you do not need to do anything. For more information, click here.

Supportal pages to check out

Here are some recently created (or updated) pages in the Supportal that you may have missed:

Latest Webinars

Our team publish regular webinars on new features and best practice. You can watch the latest webinars here.

If you need further assistance, please contact support.

Updated on April 15, 2021

Was this article helpful?

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support