The BRL currency has been added to our Stripe gateway integration.

Several TPL tokens have been added for the Order and Shipping Confirmation email templates that will allow you to customize the information displayed for the product summary. When using these tokens, you can develop custom product summaries for usage within order or shipping confirmation emails. For further information, please visit our Help Center, this information is located under the 'How to Build Custom Product Summaries' section: https://support.sticky.io/en/articles/3774146-create-customer-email-notifications

New Order requests were being rejected due to product variants that contained numeric values or special characters. This is no longer an issue.

$0.00 orders were being sent to Adyen gateway. This has been corrected.

In some cases, incorrect order totals were being sent to Adyen gateway. As of now the correct order totals will be sent.

Incorrect parameters were being sent to Adyen gateway for initial orders. We are now sending the correct parameters to Adyen for initial order requests.

When using Collection Offers, the 'lock' position was not saving when adding a product. This has been adjusted and the lock position is now saving correctly.

When attempting to add a promo code to an existing coupon profile using the API 'Update Coupon Profile' method, all of the current values were being replaced. This has been corrected.

In very few cases, when marking an order as 'fraud' using the Customers > Orders page, the order status was not updating to 'fraud'. This has been resolved.

Test Payment Methods were not bypassing the gateway and were being sent to BlueSnap. This is now working properly, and test cards will now bypass this gateway.

All orders were being sent to Avalara as 'USD' currency, even if the order was not USD currency. We are now sending the correct currency for the order.

The Product and Product Bundle import file did not have the option to include any email triggers. This has been adjusted and now includes the option to include trigger events for custom email notifications.

In some cases, the Intelligent Cascade profiles were showing 'N/A' under the 'number of gateways'. As of now these profiles should be showing the correct number of gateways assigned to the cascade profile.

When creating an order and using an invalid coupon, the “Validate” button was showing “Succesfully added coupon” even when the coupon had reached a usage limit (total or per customer). This is now working as expected.

Offer imports were not fully completing on the Insights > Import / Export data page. This is now resolved.

If the product variant had special characters, we were not displaying those characters correctly, causing sticky declines. This has been corrected.

In some cases, incorrect product prices were being sent to Avalara for refunds. This is now working correctly and the correct prices are now being sent.

The API order_view method was not returning the subtotal before discount in the response. This is has been adjusted.

The Subscription Management page was missing gateway information for some orders in a pending status. This is now fixed.

3D Secure has been added to our Adyen gateway integration!

The Order Summary on the Place Order page was not displaying the discount for prepaid offers. This has been fixed.

In some accounts both the Contacts and Customers page were enabled, causing confusion. This has been corrected.

Email notifications were using custom field values from the upsell instead of the main product. This is now resolved.

Some rebill requests were failing with Adyen gateway due to incorrect parameters being sent. This has been adjusted and is now sending the correct parameters.

In come cases, users were seeing a grey blank bar when attempting to refund from the order details. This is now working correctly.

The NMI PaySafe consent email templates have been updated to a cleaner more user friendly look.

The 'Combined Similar Address' option has been added to the Shipwire V3 fulfillment integration.

A new column for 'VAT' Tax has been added to the Custom FTP fulfillment file.

The 'Import Coupon' template was missing information causing the imports to fail. This has been fixed.

In some cases when attempting to reprocess orders, the error "Reprocessing failed on 1 order(s) Order Id # has approved order" was showing and not allowing the reprocess. This has been corrected.

When attempting to edit return profiles, the error "Expired is required" was showing and not allowing any changes to the return profile. This is now working correctly.

In few cases users were not able to remove headers from the Postback profiles. This has been adjusted and headers can now be removed.

When partially refunding an order, the cancellation request was being sent to ShipStation cancelling the entire order. This has been resolved.

Subscription Credits were throwing redundant order history notes when the subscription is in decline salvage. This has been corrected.

The delay capture option has been added to our Inovio gateway integration. For further information please visit our Help Center: https://support.sticky.io/en/articles/3730737-inovio-gateway

When resending email notifications from the order details, we will now add a note to the order history stating that an email has been resent.

We were sending a 'reference' parameter to MaxPay within our requests, causing declines. This parameter has been removed per MaxPay's documentation.

On the Customers > Reprocess Declined Orders page you can now view 250 per page, instead of only 100 or 500.

Our Restful API "Campaigns" call has been extended to support legacy campaigns.

In some cases, the 2FA authentication was not working intermittently. This has been fixed.

The criteria of 'category_id' was not working properly for the API 'order_find'/ 'order_view' methods. This has been adjusted.

When using the API 'subscription_order_update' method, if updating the quantity we were not accounting for the max quantity allowed per product. This has been resolved.

In few cases, the Decline Rule profile was ignored, and orders were cascaded even though the decline reason was blocked for cascade. This has been corrected.

When marking an order as RMA for return, the recurring was automatically being stopped in some cases. This is now fixed and working correctly.

A 'Send Test Transaction to Avalara' option has been added to the Avalara v2 profile. If set to YES, we will send test orders to Avalara. If set to NO, we will not send any test orders to Avalara.

The cancellation postback was not firing for orders that were cancelled during refund, it was only triggering for the refund. This has been fixed.

In some cases when reprocessing orders, 2 order confirmation emails were being sent. This has been corrected.

For legacy accounts, the V2 Restful API method 'Get Product' was not returning the parameter "legacy_subscription" when attempting to pull a specific Product Id. This has been adjusted and should now be working properly.

When using the API 'subscription_order_update' method to update an existing order to increase the quantity, the Forecasted Revenue field was not updating. This has been updated and the forecasted revenue field is now updating as expected.

Two new tokens have been added to our email token options : {campaign_name}

and {campaign_desc}. These tokens will allow you to populate the campaign name and campaign description in your emails.

An option has been added to our back end to allow pending orders to not be sent via postback until they are approved. Please reach out to our support team to have this option enabled.

An audit was added to the User Permissions page for internal use only, but was showing for standard users. This option has been removed.

3D Secure has been added to our Bill 1st payment gateway!

The API 'order_view' response was showing inconsistent values for refunded orders. This has been fixed.

Archived products were still showing as available to select when placing an order. This has been corrected.

In some cases, the API 'order_view' response was showing preserve = 0, even if the order was created with preserve =1. This has been adjusted and should now be working as expected.

The whitelisting IP Range was not storing the IPs within the range for single sign on (SSO). This has been corrected.

In some cases, the order history was being cut off at the bottom of the Orders page. This has been fixed.

The 'linked upsells' were not showing the order details, even if the order was created with linked upsells. This has been adjusted.

In very few cases, for PayPal V2 there were some orders that were declined but were being marked as approved. This has been resolved.

In some cases, the 'Force Next Gateway by Order IDs' v2 method was not applying to orders created 8 months or older. This has been fixed.

It was reported that the Contacts page was showing subscriptions as active when they were not active. This has been corrected.

Subscription Credits were throwing redundant order history notes when the subscription was in salvage. This has been resolved.

We have updated the ShipWire fulfillment integration to use their newest API!

In very few cases, the parent order was not being archived after successfully rebilling. This has been fixed.

The 'sub total' within the API 'order_view' response was accounting for the discount. This has been corrected and the sub total will now show the amount before any discount is applied.

When deleting users from one SSO group within the sticky portal, they were getting deleted from all groups. This has been adjusted.

We are now integrated with Revolv3 Gateway! For further information on how to configure this provider please visit our help center: https://support.sticky.io/en/articles/8233986-revolv3-gateway

No results were being shown when searching for orders using the billing address field on the Customers > Orders page. This has been fixed.

In some cases, the postback URL was sending an incorrect ancestor Id intermittently. This has been corrected.

The postback URL was sending 'is shippable'=1 even though the product on the order was not shippable. This has been adjusted and should now send the correct information.

When using the API 'authorize_payment' method, we were seeing "Required field" declines from Inovio due to the [li_value_1] parameter being sent blank in our requests. This is now resolved.

In legacy accounts, archived products were still showing as available to add when creating orders. This has been fixed and archived products are no longer showing as available when creating orders.

The 'Post to Fulfillment= No' option within the Test Payment Method was still sending test orders to Custom FTP fulfillment. This has been corrected.

Capture on Shipment and Delay Capture were not working correctly with NMI Paysafe gateways. This has been resolved.

In some cases, users were not able to log in to the mysticky.io portal due email length. This has been adjusted.

On the Reprocess Declined Orders page, we added option to search via CSV within the decline reasons field. This will allow you to search for multiple decline reasons instead of just one at a time.

Postback requests to MemberMouse were failing due to encoding issues. This has been corrected.

An issue was reported regarding postbacks not triggering for order actions on legacy accounts. This has been fixed.

In some instances, the affiliate fields were not being included in the postback requests. All fields should now be included as expected.

We were not allowing more than 1 request field within the Custom FTP profiles. This has been adjusted and now allows you to add more than 1 request field.

In some cases the Restful API 'Get Subscriptions with Filter' / order was taking several minutes to load. This should now be loading as expected.

We have a new integration with Pathly gateway! Please visit our help center for further information on how to configure this provider: https://support.sticky.io/en/articles/8113214-pathly-gateway

If the CVV started with "0" we were truncating the 0 and only sending 2 digits to the gateway, resulting in declines. This has been adjusted and the 0 is no longer being truncated in our requests.

In some cases the custom pricing was being overridden by the product price. This has been corrected.

When sending first rebills to Inovio gateway, we were not passing the 3D value "ds_trans_id" in our request. This has been updated and should now be working correctly.

The 'forecasted amount' was showing incorrectly for upsell orders on the Customers > Subscription Management page. This has been fixed.

Decline salvage functionality has been added to the BoaCompra gateway. Previously, this gateway was not working correctly with decline savage.

When creating ApplePay and GooglePay orders for Stripe, the currency field was being sent blank. This has been fixed.

In some cases Order Confirmation emails were not being triggered, this has been corrected.

Some user accounts were unable to load reports due to campaign permissions. This has been adjusted and the reports should now be loading correctly regardless of the campaign permissions.

An issue was reported regarding the custom fields parameters being sent blank within postback URL's. This has been resolved.

When placing an order from the Place Order page, when selecting the 'update tax' button, the tax was not pre calculating for Avalara V2.

We received a request to add the "merchantTransactionId" field with sticky’s order Id to the transaction API calls that are made to BlueSnap. This will populate the sticky order Id on BlueSnap reports, allowing the merchants to search transactions on BlueSnap using that ID, etc.

An issue was reported regarding the Capture on Shipment option not working correctly with recurring orders. This has been fixed.

In some cases, some order confirmation emails were not being triggered in our system. This has been resolved, and all emails should be now triggered correctly.

On the Contacts page we were displaying the EUR currency incorrectly. This has been adjusted and will now reflect properly for EUR currency.

When placing an order from existing order, if the campaign was different than the previous order, the country field was being defaulted to USA. This has been corrected.

Some instances were receiving a 500 error when attempting to mark orders as chargeback on the Customers > Orders page. This has been adjusted and there should no longer be any issues when marking orders as chargeback in the UI.

When navigating to the Contacts page from the Customers page, all of the contact records were loading to a blank page. This is now working correctly and all contacts should be loading as expected.

The 'Allow IP Address' restriction was not working for any of the API v2 restful methods. This has been fixed and the 'Allow IP Address' restriction now applies to all API methods.

The API 'prospect_find' method was not working properly when trying to use the wildcard for states. This has been adjusted.

In some cases, all orders were being sent to Avalara regardless of the states selected filter within the Avalara profile. This has been resolved and now only orders with the selected states will be sent to Avalara.

An issue was reported regarding a reprocessed order going to an incorrect tax provider. This has been corrected and reprocessed orders are going to the correct tax provider.

When using the version 2 for Fulfillment.com, the country was being sent as 'null' within the requests. This is now resolved.

In some instances, declined orders were being incorrectly preserved to gateways due to an internal setting. This is now fixed.

The Reprocess Declined Orders page has been optimized to load faster.

In some scenarios shipping charges were being applied to non-shippable products, this issue has been fixed.

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: https://support.sticky.io/en/articles/7967288-integrating-with-the-sticky-io-payments-iframe

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.

When successfully reprocessing a declined order, the order was rebilling the very next day after the reprocess, instead of rebilling 30 days from date of successful reprocess. This has been fixed.

In some cases, clients were receiving the "702- Invalid gateway Id" error when using the API 'order_force_bill' method on a subscription order. This has been corrected.

In some cases, we were rejecting orders due to specific country codes. This has been fixed, and our list of supported country codes has been updated.

When exporting orders with the criteria of 'hold', the export was showing no hold date or hold type. This has been corrected and now will show the correct information.

When issuing partial refunds, orders were being cancelled in ShipStation on single address orders. This has been resolved.

PayPal v2 was showing as available to be added to a payment router, causing issues. This was corrected, PayPal v2 is now not able to be added to any payment routing profile, being that it is an alternative payment provider.

In some cases, when refunding orders the order status and order history note were not updating on the order. This has been fixed.

An issue was reported regarding 3DS 2.0 not working correctly on the PayXpert gateway. This has been revamped and should be working correctly.

Some accounts were receiving an 800 error when processing orders for NMI gateway. Our team has made some adjustments to help prevent this from occurring any further.

When updating the customer's credit card on the orders page, in some cases the old card was being used for the rebill. This is now resolved and the new updated card is being used moving forward.

We are now integrated with SellerCloud fulfillment! For further information on how to configure this provider in your sticky.io instance: https://support.sticky.io/en/articles/7234330-sellercloud-fulfillment

An issue was reported regarding the custom price and discounts being removed when using the 'subscription_order_update' API method. This has been fixed.

In some cases there was a false rebill discount note being added to orders that didn't have the discount applied. This has been corrected.

Our 3D Verify service has been added to the Innova payment gateway integration.

In some cases, when placing an order from an existing order we were automatically applying the gateway from the previous order, instead of using the new gateway within the campaign configuration. This has been fixed.

When applying a discount directly from the Contacts page, the discounted amount was not reflecting within order details and Subscription Management pages. This has been corrected.

An issue was reported regarding orders cascading and ignoring the decline reasons condition within the cascade profile. This has been resolved and should now be working properly.

When using the restful API 'update contact payment source' method, the payment source was not actually updating within the customer wallet. This has been fixed.

An issue was reported regarding the order confirmation emails not sending in the event that the next recurring product did not have the email notification attached. This has been resolved and should now be working properly.

The Avalara V2 integration in live mode was not authenticating the credentials as expected when attempting to use the Test Connection button from the profile. This has been adjusted and should now authenticate correctly.

In some cases, the 'place new order' link from the order details was not working properly. This has been fixed.

The order_total/Calculate API call was calculating the subscription discount for trial costs, this has been corrected and should no longer calculate for trial costs.

We removed the outdated eMerchantPay gateway provider options from the Settings > Providers page. As of now only the newest version of eMerchantPay will be available to make sure you are using their latest version.

We added the PayPal V2 gateway, this is the newest version of PayPal. For further information on the new PayPal V2 version: https://support.sticky.io/en/articles/7035102-paypal-v2-alternative-payments

The option to post the tracking number to PayPal has been added when using the PayPal V2 integration. To use the tracking functionality, within your PayPal V2 profile you'll just need to set the "Send tracking info" to YES and we will send the tracking number to PayPal.

The API order_update method has been updated to support 'rebill_discount = 0'. This can be used to remove the rebill discount on an order. Previously, for the 'rebill_discount' criteria we only supported values of 1-99.

In some cases, when using eMerchantPay payment gateway we were sending an incorrect order Id within the request. This has been fixed.

An issue was reported regarding the ACI Payon gateway integration, the CAAV Value was not being encoded to the request to the gateway. This has been fixed.

In some cases, the 'Gateway Monthly Cap' notifications were sending several per percentage increase. This has been resolved.

When refunding the full order amount, the refund option was still showing for the product line items after the order had been refunded. This has been corrected.

The response was showing blank when refunding FluidPay transactions. This has been fixed.

In some cases, when using the API 'order_update' method to update the 'cc_payment_type' field, we were throwing a 500 error. This has been corrected and is now working properly.

3DS 2.0 has been added to the PayXpert payment gateway integration.

An issue was reported regarding the CVV not being sent to FluidPay for some initial transactions. This has been fixed.

Validation has been added to the Capture on Shipment option to only capture on pending orders. If the order is approved and receives a tracking number, we would not attempt to capture.

Our Avalara integration has been upgraded from the V1 version to the new V2 version.

The BRL currency was added to the Inovio payment gateway.

The 'billing address 2' value was not carrying over to the new order created when when using the NewUpsell or NewOrderCardOnFile methods. This has been fixed.

An issue was reported regarding an incorrect tax commit request being sent to TaxJar for product line items. This has been resolved.