sticky.io

Introducing the sticky.io Payments iFrame, a secure, PCI DSS-compliant method to accept payments on your website. The sticky.io Payments iFrame will allow consumers to securely enter their payment details and complete transactions on the merchant’s site without being redirected to another page. For further information please visit our help center: <a href="https://support.sticky.io/en/articles/7967288-integrating-with-the-sticky-io-payments-iframe" target="_blank">https://support.sticky.io/en/articles/7967288-integrating-with-the-sticky-io-payments-iframe</a>

- Introducing the sticky.io Payments iFrame, a secure, PCI DSS-compliant method to accept payments on your website. The sticky.io Payments iFrame will allow consumers to securely enter their payment details and complete transactions on the merchant’s site without being redirected to another page. For further information please visit our help center: <a href="https://support.sticky.io/en/articles/7967288-integrating-with-the-sticky-io-payments-iframe" target="_blank">https://support.sticky.io/en/articles/7967288-integrating-with-the-sticky-io-payments-iframe</a>

In some cases, product email notifications were being triggered on $0.00 prepaid orders at the end of the prepaid cycle.  This has been fixed.

An issue was reported regarding the Contacts page showing 'inactive' subscriptions as 'active'.  This has been corrected.

Some legacy accounts were experiencing issues using the API 'authorize_payment' method when using the Avalara V2.  This has been resolved and should now be working correctly. 

The 'DocCode' has been updated for the Avalara V2 integration to include ONLY the order Id.  Previously we were including the date and order Id as the 'DocCode', this was causing reconciliation issues within Avalara. 

- In some cases, product email notifications were being triggered on $0.00 prepaid orders at the end of the prepaid cycle.  This has been fixed.
- An issue was reported regarding the Contacts page showing 'inactive' subscriptions as 'active'.  This has been corrected.
- Some legacy accounts were experiencing issues using the API 'authorize_payment' method when using the Avalara V2.  This has been resolved and should now be working correctly. 
- The 'DocCode' has been updated for the Avalara V2 integration to include ONLY the order Id.  Previously we were including the date and order Id as the 'DocCode', this was causing reconciliation issues within Avalara. 