Add-On products were showing $0 forecasted revenue within the contacts page and certain API calls, regardless of the price being greater than $0; this has been resolved and the correct forecasted revenue is now showing.

Orders voided through Braintree Payments were being sent as refunds to Avalara, this has been resolved and they are now being sent to Avalara with the correct voided status.

The system was processing refunds on PayPal orders through Braintree Payments, regardless of existing open disputes, this has been corrected and the system is now checking for open disputes on PayPal orders, specifically through this gateway, before processing a refund.

A new Delayed Capture option has been added to the Sticky.io 2.0 gateway integration.

A new Kount version is now available: Kount360. Please reach out to your Client Success Manager if you’re interested in migrating, they’ll be happy to assist you!

Clients that have a combination of campaigns using our legacy product, and campaigns using offers, were not able to add new products to their legacy campaigns, this has been resolved.

Some clients were experiencing issues when attempting to cancel an Add-On product from the customers page, this has been resolved.

Processor responses are now being captured with Revolv3 gateways.

Smart Retries now supports “Payment Rerouting” where you can reroute the attempts to a different gateway than the original, you can choose on what attempt number you’d like to start rerouting to the new gateway and you can preserve that new gateway as well.

We’re now integrated with Saleshield gateway, you can find how to configure this gateway in our help article here.

When using manual Sale Tax Profiles the system was defaulting to NY State when no zip code was submitted, this has been resolved so that no taxes are added if the zip code is not present.

A new token has been added to the email notification tokens: {customerserviceemail}. This will populate the customer service email from your gateway profiles.

The system notification email that is sent to you when the gateways within your Payment Routing profile reach the Decline Limit Threshold, will now include a summary of the decline reasons, for added transparency.

We’re now integrated with Airwallex gateway, please feel free to take a look at our help article for more details: https://support.sticky.io/en/articles/12785488-airwallex

The Campaign Descriptor will now apply to NMI gateways when used within the Payment Router and Cascade profiles also, not only when a single gateway is used directly in the campaign.

We now have the Stripe Connect V2 integration, which supports Stripe Link as well as the most up to date methods for GooglePay and ApplePay implementations recommended by Stripe.

A very requested integration is now available: Klarna, please feel free to click on the link to learn more about it.

Merchants were experiencing errors when attempting to use GooglePay with our NMI integration, this issue has been resolved.

When using the “delay_confirmation_notification” parameter with the NewOrder call to aggregate product information from multiple orders into one, the tokens for sales tax and shipping were not working properly, this has been fixed.

When an order with multiple subscription products was voided, the system was triggering the cancellation email multiple times, this has been fixed.

For legacy accounts, custom billing cycles were being ignored for ‘offline’ payment type orders. This has been resolved.

Some users were unable to schedule reports, this has been resolved.

We were experiencing issues with some of the refunds sent to CyberSource, this is now fixed.

We are now integrated with Give Payments! For further information on how to configure this provider: https://support.sticky.io/en/articles/12509904-give-payments

The Cardflo payment gateway was having issues with the CIT/MIT parameters. This has been corrected.

Some clients were receiving AVS declines when using BrainTree Payments gateway due to the billing address information not being included in the request. This is now resolved.

Our Reprocess Declined Orders page has been optimized to show declined orders within 1 hour of being created. Previously it took 2 hours for the declines to show on this page.

When an order was forced to one Braintree Payments gateway to a different Braintree Payments gateway, we were sending the payment method from the original gateway to the new gateway instead of starting the process by creating the customer and tokenizing the cc number. This has been fixed.

In some cases the global default decline manager profile was retrying the order instead of placing it on hold. This has been corrected.

Several clients were receiving '502 Bad Gateway' responses when trying to use various API methods. Our team has made some adjustments to help alleviate these type of responses from happening.

Even if no 3D parameters were included in the New Order request, we were sending '3ds.enabled=true' to Checkout.com gateway due to the gateway profile having 3D verify enabled. This has been corrected, and now we will only be sending "3ds.enabled=true" if there are 3D parameters included in the request as well as 3D being enabled within the gateway profile.

The 'queue status' filter has been removed from the Reprocess Declined Orders page.

In some cases we were not sending card updates to Revolv3 as expected. This has been fixed.

Currencies BRL, CLP, COP, PEN, UYU, and CRC have been added to the Stripe gateway integration.

We added the option "Use AVS?" to the Cybersource gateway profiles. If enabled, this will send over the AVS information to Cybersource for transaction requests.

Some orders that were voided on BrainTree Payments gateway were not being properly sent to Avalara. This has been fixed.

When refunding orders through RocketGate gateway, we were misinterpreting the response, causing refund declines. This has been corrected.

In the case that the order total was over $1,000.00 we were sending an incorrect amount to BrainTree. This has been resolved and the correct amount is now being sent regardless of the order total.

The PAYPAL* prefix was not auto appending to the descriptor for BrainTree payments/ Paypal orders. This has been fixed.

For both initial and recurring orders, the API Order Total Calculate method was throwing an incorrect calculation due to invalid base/unit price. This has been corrected.

Our team resolved an issue where tracking numbers were not being properly sent to PayPal V2.

In some cases, the API order_update method was not allowing the credit card to be updated on orders. This method has been adjusted and should now be working correctly.

When using the API authorize_payment method, we were reusing the temporary order Id's provided in the response. Our team has resolved this issue, as of now we will not be reusing the temporary order Id's.

For the Acquired gateway, orders were not posting correctly when using either the force gateway or the API NewOrderCardOnFile methods. This is now working as expected and orders are posting correctly.

Additional parameters are now being sent to Inovio gateway to allow CIT/MIT for Mastercard orders.

When voiding ApplePay or GooglePay orders, the void request was not being sent to Avalara. This has been fixed.

The V2 API order-total/calculate method was missing from the API Accounts permissions page. This method has now been added.

In some cases, when using PayPal v2 the tracking numbers were not being sent to PayPal. This has been corrected.

In some cases, consent emails were not being sent due to a 500 error. This has been fixed.

The Finix gateway integration was sending the order request a penny off of the order total. This has been corrected.

For PayPal V2, the stored transaction Id was different than the upsell and was not searchable within PayPal. This is now resolved.

We are now integrated with the Nuvei Paymentez gateway! For further information on how to configure please visit our help center: https://support.sticky.io/en/articles/11740345-nuvei-paymentez-gateway

An error message will now be added to the order history note if an Avalara V2 profile is misconfigured with the wrong credentials, and there will be no tax added to the order.

The 'copy' function was not working properly on Coupon profiles. This has been fixed.

An issue was reported where a partial refund was sent to Quantum Qoin that was approved, but then when going back to complete the rest of the refund, Quantum Qoin rejected it and the order changed from Approved to Declined. After further investigation, our team can confirm that this gateway does not support partial refunds, only full refunds are supported.

The query has been optimized on the Reprocess Declined Orders page to improve response times on initial load and when applying filters.

When rendering the HTML for the PayPal V2 redirect, there was a '>' symbol showing at the top of the page. This has been corrected.

In very few cases, we were seeing issues with orders not being sent to SellerCloud fulfillment. This has been fixed.

When attempting to refund orders on the Quantum Qoin gateway, if the refund failed the order status was changing from approved to declined in some cases. This is now resolved.

The JCB payment type has been added to the Products > Campaigns page under the 'Payment Types' section. This payment type can be used with JPY currency when using the Checkout.com gateway.

The BrainTree V2 gateway decline response for 'Insufficient Funds' was showing as 'Processor Declined'. This has been updated to reflect the proper decline reason of 'Insufficient Funds'.

The Legacy API 'subscription_update' method was not allowing the reset recurring for upsell subscription Ids. This has been fixed.

Refund failures from Revolv3 gateway were showing an 'Unknown Response from Gateway' reason within the order history. This has been corrected and the refund failures now are showing the correct refund failure reason.

In some cases, the 'Payment Routing Decline Threshold' system notification was not being triggered as expected. This has been fixed.

On the Customers > Orders page, we added an "Authorization Code" filter, which will allow you to search by the order's authorization Id.

In some cases the currency value was being sent as blank to Stripe for ApplePay and GooglePay orders, causing declines. This has been fixed.

In very few cases, the subscription information was not loading on the Contacts page. This has been corrected.

The API 'coupon_validate' response was only including 1 product even if the request included multiple products. This has been fixed.

In some cases, the copy function within the SMTP profiles page was not working. This has been corrected.

Our team also resolved an issue where some gateway profiles were not opening when attempting to edit.

In few cases, incomplete orders were blocking other orders to be created due to the single purchase limit. This is now working correctly.

We are now integrated with CCBill Gateway! For further information on how to configure this gateway, please visit our Help Center: https://support.sticky.io/en/articles/10845380-ccbill-gateway

Our development team resolved an issue where the {orderid} token in the subject line for email notifications was not being populated with the order Id.

If the order had two variants of the same product, the email notification was only including one of the variant names in the message and ignoring the others. This has been fixed.

The API V2 GET Products response was returning 'null' for some variant fields. This has been corrected.

Some clients were experiencing longer load times when attempting to open up the payment routing profile. Our development team has optimized the load times on this page to correct this issue.

When attempting to export CSV from the Products page, it was exporting all products instead of the specific products selected. This has been fixed.

The Reprocess Declined Orders page table and scroll bar have been expanded to show all information on the page.

We added a 'Refund Reason' column to the Insights order exports. This will show if you have the refund reason disposition note configured.

Some clients were receiving a 'Syntax Error' when attempting to use ShipBob Fulfillment. This has been corrected.

If attempting to change your user password, we were not allowing certain special characters. Now there will be a pop up showing which special characters are supported.

Special characters were not being properly added to the email subject. This has been fixed.

In some cases, the shipping address was not being sent to PayPal resulting in 'The shipping address is required' declines. This has been resolved.

Refunds and Chargebacks were not being sent to Kount, this has been corrected.

In very few cases, the API 'order_void' request was taking longer than expected to provide a response. This has been fixed.

Our team addressed an issue where PayPal providers were unable to be removed from campaigns even if they had no orders associated.

The forecasted next charge amount on the Subscription Management page was not matching the order detail amount. This has been resolved.

A new System Notification has been added for when SMTP profiles are disabled. This is located on the Settings > System Notifications page.

The Checkout.com integration has been enhanced to include a '3ds.enabled=true' parameter, which is needed for EU transactions.

Some clients were receiving an alternative payment type error when attempting to force orders to the next gateway using the Subscription Management page. This has been fixed.

In very few cases, the 'Manage Product' section within the Contacts page was not loading any data. This has been corrected.

The Subscription Management page was showing a payment router as the next billing gateway for alternative provider orders. This has been resolved.

Our team addressed an issue where the shipping address provided in the NewOrderWithProspect call was being ignored, and the order was being created with the prospect address instead.

3D Secure has been added as an option to the RocketGate gateway! For further information on how to configure, please visit our Help Center: https://support.sticky.io/en/articles/3739381-rocket-gate-payment-gateway

3D Secure has also been added to the Genesis gateway! For further information on how to configure, please visit our Help Center: https://support.sticky.io/en/articles/3730575-genesis-gateway

For Stripe orders the 3Ds response was not being properly interpreted for reprocessing/initial dunning. This has been fixed.

The API 'coupon_validate' method was intermittently throwing unexpected errors. This has been adjusted.

Our team identified and corrected an issue with our Revolv3 gateway integration that was causing subsequent partial refund attempts to fail.

Our Checkout.com integration has been enhanced to allow NewOrderCardOnFile orders.

The Stripe integration has been updated to include a 'radar_session' parameter in our requests to Stripe.

Changes were made to the Bill 1st gateway integration to ensure we are mapping the correct decline reason for declined orders.

When using the API 'order_force_bill' method, it was ignoring any coupons applied. This has been fixed.

In some cases, newly copied gateway profiles were showing an error under the 'Merchant Account Details' tab when attempting to save. This has been corrected.

Alternative Payment providers (PayPal, ApplePay, GooglePay) were not able to be removed from campaigns, even if there were no orders yet created on them. This has been adjusted, and these providers can now be removed from the campaign as long as there are no active recurring orders on them.

Our team has implemented some changes to prevent digital wallet-based payments (PayPal, Apple Pay, Google Pay, etc.) from being rerouted to unsupported payment gateways. This change applies to the Campaigns page as well as the Subscription Management page.

We introduced a "Get MIDs" button into the sticky menu, positioned to the left of the existing "New Order" button. When clicked, the button will trigger a lead application form that is then sent directly to our sales representative.

The Quantum Qoin gateway has been updated to ensure that we are mapping the correct decline reasons.

A fix has been applied to the PayExpert payment gateway to ensure that 3D Secure is working properly.

The 'utm_term' parameter was not sending any values via postback, this has been corrected.

GBP and EUR currencies have been added to the Bill 1st gateway.

CAD currency has been added to the SafeCharge/NUVEI gateway.

A new checkbox labeled "Grace Period" has been added as an option to the decline rule profiles. If selected, it will block the grace period from taking effect.

When including 'is_preserve' = 0 within the API V2 PUT 'Update Next Recurring Price method' request, the custom price was not applying. This has been corrected.

In very few cases, the Prepaid Offer was recurring into an incorrect Product ID. This has been fixed.

An error was being thrown when attempting to force bill an order that recently had a subscription credit applied. This is now resolved.

An adjustment was made to the Vantiv gateway request to enforce that we are sending the correct transaction Id field.

A new 'auth-id' parameter has been added to our API 'order_find' method to allow you to search by the authorization Id.

We are now integrated with SolvePath gateway! For further information on how to configure this provider in sticky, please visit our help center: https://support.sticky.io/en/articles/10374391-solvepath-gateway

Due to some confusion when deleting a gateway from the payment router, the pop up window message has been adjusted to show "Continue with delete?"

Our BrainTree integration has been updated to use their newest SDK, this is now under the 'BrainTree Payments' gateway profile in sticky. For further information on how to configure this provider in sticky, please visit our help center: https://support.sticky.io/en/articles/10374500-braintree-payments

When attempting to use the PayExpert gateway, several clients were receiving errors due to 3D Secure. This has been fixed and the 3D Secure for this gateway should now be working correctly.

Regarding FlexCharge, MIT orders with "Stop the recurring after the next successful billing" were being cancelled before receiving the FlexCharge response. This has been corrected.

When an order is manually updated to shipped and then refunded, we were adding a false note stating that the product will not be sent to fulfillment because it has been fully refunded. This has been adjusted and that note should no longer appear.

For Paypal orders, if the 'Use Wallet Info' is set to YES within the gateway profile and we do not receive any shipping information from the PayPal response, we will now be adding a "Not all PayPal information was passed" order history note.

We are now including the parameter "merchant_initiated=true" within our requests to Checkout.com for all MIT recurring orders. This is to prevent "The endpoint did not accept the request. (Code: 422) token_cryptogram_missing" declines.