Some clients were noticing a delay within the Customers page. This has been fixed.

Returns from Fulfillment.com were not being updated correctly in sticky.io. This has been corrected.

We added a new Restful V2 API method called "Remove Coupon". This method can be used to remove order level coupons from orders.

Additional email tokens {website} and {gateway_brand_image} have been added to support additional information from the payment gateway profile. These tokens will allow customers to include specific details tied to their payment gateway in emails triggered by payment-related events, such as order confirmations, refunds, and subscription reminders.

In very few cases, some clients were not able to add additional products to the offer. This has been corrected.

The cancellation emails were being sent incorrectly for orders where the upsell product was cancelled. This has been fixed.

The Restful V2 API 'Update Next Recurring Price' method was not updating the next recurring price in the UI. This has been adjusted, and now the new updated price will reflect properly in the UI.

We resolved an issue regarding the customer's billing name not being sent correctly to Kount, this was causing the name to show as blank within Kount.

The Restful V2 API 'GetCampaign' method was showing additional coupon profiles that were not assigned to the campaign. Now this method will only display the details of the coupon profiles assigned to the specific campaign.

The Fulfillment Lab integration has been updated to use HTTPS instead of HTTP, as some clients were noticing issues with orders not being sent to fulfillment.

In few cases, an incorrect payment token was being sent to Stripe and Checkout.com, causing declines. This has been fixed.

Additional parameters have been added to our Adyen gateway requests to support pre authorizations.

In some cases, when using PayPal V1 some orders were showing as declined in sticky due to abandonment, but approved in PayPal. Our team has implemented a fix that should prevent this issue from happening any further.

An issue was reported regarding some issues not being sent to ShipStation fulfillment. This has been resolved.

In our requests to Kount for some orders we were including either an apostrophe or an accent mark in the address, causing Kount to over block the orders. This has been corrected.

For orders created using the 'Relative Date' billing model, we are now adding an order history note if the relative date was changed.

In very few cases the system was taking several seconds when attempting to copy campaigns for advanced routing.

If the last 4 of the credit card was ending in 0000, we were displaying it in the order details as "XXX0". This has been fixed.

When attempting to update a user's permissions, the 'something went wrong' error was appearing. This has been corrected.

Gateway profiles on the Providers page were unable to be disabled, due to an error stating that the gateway had active orders. Our team has applied a fix that will allow you to disable the gateway profile as long as there are no orders on it.

Refunds via Revolv3 gateway were failing due to an incorrect invoice ID being sent in the response. This has been adjusted, and the correct invoice ID is now being sent.

In very few cases, FlexCharge orders were remaining as pending in sticky due to the webhook service being temporarily down. Our team has applied a fix for this scenario, we will continue to reattempt and if still not successful we will be adding an “Order could not be sent to Payment Recovery Service” note to the order details.

In some cases, the 'total forecast' field was not populating on the Subscription Management page. This has been fixed.

The PayExpert payment gateway was having 3D redirection issues. This has been corrected.

Our CardFlo payment gateway request has been updated to indicate Custom Recurring Schedule.

The Subscription Management page advanced search has been updated to include 'Billing Date From' and 'Billing Date To' fields.

ZAR currency has been added to the BrainTree gateway.

The API 'order_find' method has been updated to include pending orders when searching by the customer's email. Previously, pending orders needed to be pulled separately.

In some cases, orders were not being successfully committed in Avalara. This has been fixed.

When attempting to select additional campaigns within User Permissions, we were not allowing all campaigns to be selected. This has been corrected.

We are now integrated with CardFlo gateway! For further information on how to configure this provider in sticky: https://support.sticky.io/en/articles/9821123-cardflo-gateway

In some cases, coupons applied to $0 trials were resulting in negative amounts sent to the gateway and declining, this has been corrected so that if the coupon is a lifetime coupon it only applies to future recurring orders as long as the amount is greater than $0.

When using headers for subscription postbacks, they were failing for "error":"Missing credentials." This has been fixed.

Inside of payment routing profiles the verbiage within the help bubble for Mid Group Routing has been adjusted.

The "Payment Failed" prefix was removed from Revolv3 declines.

We removed the option to create "Checkout 2.0" profiles on the Providers page, as all clients should be using the "Checkout.com (REST)" profiles moving forward.

In some cases, disabled SMTP profiles were still relaying emails. This has been fixed.

Our team resolved an issue regarding incorrect tokens being sent to Checkout.com, which was causing "source_id_invalid" declines.

The delay capture cron was not picking up all eligible orders in few cases. This has been corrected.

When using ApplePay, we will now be storing the first six and last four from the BrainTree response, so that chargeback providers are able to map correctly.

ApplePay transactions were being sent to Kount with the same 'PTOK' value, causing further issues with customers being linked to the same persona. This has been resolved.

Orders processed via Reach gateway were not accurately being accounted for within the payment router monthly cap. This has been fixed.

Some clients were receiving "Unusable_address" declines on the Reach gateway. As a solution, our team as made some adjustments to the gateway request to prevent this decline from happening any further.

Postbacks were not being properly triggered for orders created on the Reach gateway. This has been corrected.

When attempting to process 3D transactions through the Quantum Qoin gateway, they were failing due to the ECI code being passed incorrectly. This has been adjusted, and the ECI should now be sending correctly to Quantum Qoin for 3D orders.

Orders created via Single Sign were showing blank in the "created_by_user_name" parameter within the API 'order_view' method. This has been resolved.

An order history note was added to FlexPay orders that are placed on hold due to Hard Declines.

We were not allowing the deletion of unused gateways in some accounts. As of now, any gateways that have not been used can still be deleted.

The Insights exports have been updated to include a column for promo code.

When importing refunds with the refund type 'reconcile', we were still sending the refund request for PayPal orders. This has been fixed.

For FlexCharge orders, in some cases when the order rebilled and failed, we were not allowing the parent order to enter into decline manager. This has been corrected.

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

The Pay.com gateway integration has been deprecated.

3D Verify was not working properly with the PSI Gate gateway, this has been fixed.

When marking an order as chargeback using the API, the 'hold type' was showing as 'unknown'. This has been corrected, and will now show the correct hold type.

The Restful v2 Subscriptions 'Update Next Recurring Product' method was not allowing pending orders to be updated. This has been adjusted, and this method will now allow changes to pending orders.

Our requests to Revolv3 gateway have been updated to include additional information. This update will provide transaction context, increasing approval rates for subscription-based transactions.

CIT/MIT options have been added to the FlexPay gateway profile.

In some cases, incorrect descriptors were being sent to BrainTree. This has been fixed.

An update was made to the Reprocess Declined Orders page, to remove any non credit card orders from showing as available to reprocess.

When using ApplePay with Checkout.com, we were seeing "encrypted_data_required, public_key_hash_required, signature_required, transaction_id_required, version_required" declines. Our development team has made some changes to avoid these declines.

In some cases test orders were being sent to Transaction Select, causing declines due to fraud. This has been corrected, and test orders will no longer be sent to Transaction Select.

When creating offline orders in the Legacy environment, the One Time Paired products were not automatically applying to the orders. This has been fixed.

For FlexPay orders, in some cases the wrong parent order Id was being attached to the order history notes. This has been adjusted, and the order history will now reflect the proper parent order Id.

Custom Fields were not able to be deleted from the product configuration. This has been corrected and now custom fields can be deleted from products if needed.

An issue was reported regarding BIN profiles not blocking BINs configured within the BIN profile. This has been revised and BINs should now be blocked as expected.

In very few cases, decline manager attempts were being sent to a FlexCharge gateway, instead of the original gateway on the order. This is now resolved.

The following processors have been added to the Processor list within the gateway profiles: Axiom, BMO, Corvia, Esquire, Maverick, Missionvalley, Nuvei, PAYARC, Quantum, Signapay and Synovus.

When using the BRL currency, we are now sending 'fields_document_id' in our requests to Stripe.

When selecting the 'Stop on Next Rebill' option within the order details, you will now be prompted to select which subscription Id you would like to stop. This will allow you to stop the recurring on a specific subscription Id in the order, but still allow others to successfully rebill.

The Bill 1st gateway integration has been updated to support forced subscriptions. This will allow you to force existing subscriptions from another gateway into Bill 1st without issue.

Orders that were declined due to prepaid cards not being allowed were being sent to FlexCharge. This has been corrected, and sticky.io declines due to prepaid cards will no longer be eligible to be sent to FlexCharge.

The Restful API v2 'Force Next Gateway by Order IDs' was forcing the order to the gateway several times. This has been fixed.

When cascading orders to multiple tokenized gateways, incorrect tokens were being sent, resulting in declines. This has been adjusted, and orders should now be able to cascade to multiple gateways as expected.

Orders that were approved via FlexCharge were not triggering the postback URL. This has been resolved, and the postback will now trigger for approved FlexCharge orders.

BrainTree orders that were cascaded and salvaged by NMI were not able to be updated. This has been fixed.

The 'next_subscription_product_price' within the API 'order_view' response was not considering coupons. This has been resolved.

When attempting to use GooglePay with Checkout.com, some clients were receiving "The endpoint did not accept the request" error. This has been fixed.

In very few cases, some subscriptions were billing outside of their relative billing date. This has been corrected.

When changing the payment router in a campaign, we were allowing you to save the campaign without specifying whether or not you would like to 'maintain existing gateways'. This has been adjusted, and the popup will now require you to make a selection before saving the campaign changes, to prevent further issues.

A 'Post Descriptor' yes/no option has been added to the Authorize.net gateway profiles. If this is set to YES, we will send the descriptor from your gateway profile to Authorize.net within our requests.

In some cases, recurring orders that contained a shippable product were showing as 'No Shipping Needed'. This has been fixed.

When creating new payment routing profiles, the currency was showing as 'unknown'. This has been corrected and will now display the correct currency for the payment router.

When using the Sales Tax profiles, if a decimal was included we were rounding up the decimal after the profile was saved. This has been adjusted and the decimal is now saving correctly.

In few cases, some clients were not able to assign Kount to all of their campaigns. This has been fixed.

An issue was reported regarding some orders being created but not showing within the UI. This has been corrected.

The shipping method was not being sent to ShipHero for fulfillment requests. This has been updated, and the shipping method is now being sent.

In very few cases, advanced routing configurations within the payment router were not saving correctly. This has been corrected.

When attempting to update the prospect email address using the API 'prospect_update' method, we were returning an unexpected response code of 358. This has been adjusted and will now return the proper response code of 343.

The Single Purchase Limit used to block manual recurring declines reprocess, this has been removed to make this page logic congruent with the automated recurring processes and it will continue to apply to initials.

In some cases, cascaded orders were being sent to Avalara for each cascade attempt. This has been fixed.

The counties England, Scotland, Wales, and Northern Ireland were not listed when placing an order in the UI via the place order page, when selecting the country UK/Great Britain. This has been corrected.

When stopping the recurring on an upsell, the API 'order_view' was showing an incorrect recurring date for the upsell product. This is now resolved.

The "billingSameAsShipping" parameter within the API 'NewOrder' call was not correctly applying the billing address for PayPal orders. This has been adjusted, and now when using this parameter the shipping address is applying to the billing address as expected.

A recent adjustment to the Subscription Management page only allowed actions up to 250 per page. This adjustment has been removed, and will allow more than 250 but we do not recommend to exceed more than 700 total.

Promo codes have been added to the exports pulled from the Products > Coupons page. Previously, when exporting coupon profiles from this page the promo codes were not included.

When using the Bill 1st gateway, we were sending the country code "360" instead of "036" for Australian customers. This has been adjusted and we are now sending the correct country code.

When orders were placed on hold using the API 'Stop Recurring On Next Rebill' option, the hold type was showing as 'unknown' within the API 'order_view' method. This has been fixed.

In very few cases, orders in sticky were showing as success, but declined in Checkout.com. This has been corrected.

The legacy API 'subscription_update' method was showing response code 100 when resetting the upsell subscription, but the upsell isn't actually reset. This has been fixed and should now be working correctly.

A 'provider_response_code' parameter has been added to the NewOrder API response for orders placed using Quantum Qoin gateway. This parameter is specific to processor declines.

3D Verify has been added to the Quantum Qoin integration. For further information please visit our Help Center: https://support.sticky.io/en/articles/8980451-quantum-qoin

A new parameter called 'ip_address_lookup' has been added to the API 'order_view' response. This will provide you with the location of the IP address.

If the product name had double quotations included, we were not saving the product name correctly. This has been fixed.

When using Genesis payment gateway, some clients were receiving "IP address is not whitelisted" declines. This has been corrected.

Also regarding Genesis payment gateway, we were not including all correct parameters in our requests, causing various declines. This has been adjusted on our end and should now be working correctly.

In some cases, when using Bill 1st gateway some clients were seeing "ERROR Duplicate transaction data submitted for SubscriberID in the past 5 MINUTE" declines. To resolve this, we added the 'AllowDuplicateSignup="1' parameter to the Bill 1st request, to prevent this issue moving forward.

The 'campaignId' parameter has been added to the API 'prospect_update' method, to allow you to change the campaign Id of the prospect.

A 'Time Zone' field has been added to the ShipHero fulfillment profiles, to allow you to change the time zone for orders sent to ShipHero.

Within the cancellation email notifications, the {productname} token was not populating for any orders that were cancelled using the API 'subscription_order_update' method. This has been fixed.

When creating orders or making changes via API we were showing in the order history 'by sticky.io'. This has been updated, and the order history will now show the API username that created the order or made the update etc.

In very few cases, $0.01 refunds were being sent to Avalara when marking an order as RMA. This has been resolved.

The Square integration has been deprecated.

In some cases, when refunding orders on Adyen gateway the orders were being refunded correctly, but we were showing an order history note that the order was not able to be refunded, causing confusion. This has been corrected.

We added an 'additional_variant_id' parameter to our API 'subscription_order_update' method, to allow you to add product variants to existing orders.

The promo code has been added to the Restful v2 GET Coupon Profile response, previously this response did not include any promo codes.

Special characters within the customer email address were showing incorrectly within the UI. This has been fixed.

In some cases, when making changes to an existing postback profile and attempting to save, an 'invalid request' error was being shown. This has been corrected, and existing postback profiles can now be edited and saved.

Any orders created in a pending state via the 'Capture on Shipment' method were not being sent to Avalara. This has been corrected.

$0.00 orders were being sent to Adyen gateway, this has been resolved.

Our Genesis gateway integration has been fully updated and should now function properly! For further information on how to configure this provider in sticky:https://support.sticky.io/en/articles/3730575-genesis-gateway

'Customer Name' and 'Customer Email' columns have been added to the Reprocess Declined Orders page. We also added an 'exclude' option to the "Recent Customer" filter.

An option to hide test orders has been added to our Subscription Management page. This option will allow you to filter out any test orders.

'consent_required' and 'consent_received' parameters have been added to our API 'order_view' response, to indicate if the order requires consent or if the consent has been applied.

The option to add product variants to existing orders has been added! Previously we only allowed you to add products to an existing order, now you can add product variants as well.

A 'Post Descriptor' option has been added to the Revolv3 gateway profiles, to allow you to send the descriptor from your sticky profile to Revolv3.

Our Stripe integration has been updated to send customer and payment information to Stripe within our requests.

The ZAR currency has been added to the PayPal V1 integration.

In some cases, clients were seeing 'unknown' listed as the 'hold type' for orders on hold. This has been fixed, and now no orders should show with the hold type as 'unknown'.

When blacklisting orders that were placed on the dry run testing gateway, the orders were not automatically being placed on hold. This has been corrected.

The 'Delayed Capture' option has been added to the Authorize.net payment gateway profiles. For further information on how to configure this within your gateway profile, please visit our help center: https://support.sticky.io/en/articles/3727278-authorize-net-gateway

Our Payment iFrame now allows for you to customize the size, color, and font! For further information please visit our help center: https://support.sticky.io/en/articles/7967288-integrating-with-the-sticky-io-payments-iframe

The postback {product_prices_csv} token was not accounting for any product custom pricing or product coupons. This has been fixed, and this token now will account for both custom pricing and product coupon discounts.

In very few cases, the Stripe 3D failed but we still created an approved order in sticky. This has been corrected.

Our Revolve3 payment gateway integration has been updating to always send the payment descriptor from the sticky.io gateway profile.

A notification window has been added to the Settings > Providers page when disabling a provider profile. The notification states that when disabling a provider profile, you must also remove that profile from your campaigns as well.

In some cases when using Adyen gateway, orders in sticky were remaining pending even though we received a successful webhook from Adyen to complete the order. This has been corrected.

The restful v2 'Get Campaign' API method was returning the order status of 'cancelled' when the order status was 'hold'. This has been adjusted and this method will now return the correct order status.

In very few cases, refunded PayPal orders were not being sent to Avalara. This has been resolved.

In some cases, we were miscalculating taxes from Avalara, causing $0.01 refunds. This has been fixed.

Some clients were seeing blank PayPal V2 declines with the reason "Declined by Payment Gateway ()". This has been corrected and will now show the correct decline reason as expected.

We are now integrated with Quantum Qoin Gateway! Please visit our Help Center for further information on how to configure this provider in sticky: https://support.sticky.io/en/articles/8980451-quantum-qoin-gateway

Recently we received a request to add the 'vertical Id' column to the Product import file, this was causing issues as the vertical Id was being required. This has been resolved, and the vertical Id is no longer required in the product import.

There were issues with the mapping of payment method parameters within our integration with Revolv3, leading to failed transactions due to null values being passed. This has been corrected, and the correct parameters will now be sent to Revolv3.

The Restful API call to add custom fields was rejecting ALL requests, this has been corrected and is now working as expected.

We have adjusted the way US orders show in sticky, previously it was showing "United States of America (the)", now it will show as "United States of America".

In very few cases, if the order had multiple products and placed one of them on hold, we were automatically cancelling the entire order. This has been fixed moving forward.

Within the API 'order_view' response, we were showing 'refund_amount=0' at the product level, even if the entire order was refunded. This has been adjusted and will now reflect the correct refund amount.

In some cases, we were sending an incorrect refund amount to Avalara. This has been resolved.

Our PayPal V2 integration now supports subscriptions! Now you will be able to process subscriptions using this gateway, previously it was straight sale only.

In some cases, orders were not receiving a new retry date from Smart Dunning. This has been fixed.

The API 'order_force_bill' method response was not including the gateway Id that the order processed on. This has been adjusted, and the response will now include the gateway Id.

When using Collection Offers, some orders were being created with an incorrect amount of products. This has been corrected.

In very few cases, when the rebill order attempted to bill and failed, the parent order was being placed on hold, preventing decline salvage. This has been resolved, and moving forward the previous order will remain active and eligible for decline salvage attempts.

A 'Type' search column has been added to the Settings > Providers page, to allow you to easily search for provider profiles by type.

The API 'payment_router_view' method was returning a 709 error when including a CSV of payment router Id's in the request. This has been fixed.

Orders containing special characters were being rejected by the system when placing orders in the UI. This has been corrected.

Orders were being created with dummy shipping/billing information when using PayPal V2. This is now resolved.

When using the PayPal V2 profile in 'Test Mode'= YES, the shipping address information was not being sent to PayPal. This is also resolved.

The Restful V2 API was not accounting for campaign restrictions within the API user account. This has been adjusted, and the v2 now will account for all campaign restrictions on the API user account.

FlexCharge transactions will now be cancelled if the order is blacklisted, previously blacklisted orders were still attempting to send to FlexCharge.

Our product import was missing columns for vertical, product weight and declared value. These columns have now been added to the product import file.

The API 'payment_router_view' method was returning an incorrect amount of gateways. This has been fixed, and this method now has pagination to include all gateways within the payment router.

For legacy accounts, when archiving a product, that archived product could not be edited as the next subscription item was changing to a non archived item. This has been corrected.

"Card Or Magstripe Required" rebill declines were occurring on the Card Knox payment gateway when attempting to force rebills from a different gateway to Card Knox. This issue has been resolved.

When reprocessing a declined orders, the order history note will now show the users name that queued the reprocess, previously it just showed "By sticky.io".

Test card refunds were being sent to the Checkout.com gateway. This has been fixed.

In some cases, orders were being marked as chargeback in the UI, but the order status did not update to reflect the chargeback. This has been corrected.

Incorrect payment data was being sent to Checkout.com causing 'source_id_invalid' declines. This issue has been fixed and we are now sending the correct payment data.

We are now integrated with Netevia payment gateway! For further information on how to configure this provider within sticky: https://support.sticky.io/en/articles/8780507-netevia-gateway

GooglePay has been added to our BlueSnap payment gateway integration, for further information:https://support.sticky.io/en/articles/6172439-bluesnap-gateway

Our Great Lakes Fulfillment integration has been updated to 'Jetmail / Great Lakes Fulfillment'. We also added an "Auto Ship On Rebills" option to the profile, you will need to set this to YES if you would like the auto ship indicator to be sent to Jetmail/Great Lakes Fulfillment. For further information: https://support.sticky.io/en/articles/3746603-jetmail-great-lakes-fulfillment

The order details page has been updated to allow you to change the recurring date for add on products. This will allow you to change the recurring date for any add on products in the order.

A 'retry_attempt' parameter has been added to the API 'order_view' response to indicate which attempt the order is on if the order is in decline salvage.

In some cases, the 'product' section within the Contact record was not populating correctly. This has been fixed.

We were receiving "cURL error 56: Received HTTP code 407 from proxy after CONNECT" declines from the CardKnox payment gateway integration. This has been corrected.

Some contacts were missing information within the 'transactions' tab on the Contacts page. This has been resolved.

In few cases, new gateways were not able to be successfully added to the payment routing profile. This is now fixed, and gateways can be added as normal to the payment router.

When updating the permissions within the employee department templates, those new permissions were not reflecting on existing user accounts containing that department. This has been adjusted and the updated permissions are now applying as expected.

An option was added to our back end that will prevent postbacks from firing on pending orders. If you would like this option applied to your account please reach out to our Support Team for further assistance.

The Merchant Customer Id was not being sent within the requests to RocketGate gateway. This has been corrected and we are now including the Merchant Customer Id in our request to RocketGate.

In some cases when removing the force gateway from a recurring upsell, the force was not being removed. This has been fixed moving forward.

There were some column issues within the Custom FTP Fulfillment CSV file. This has been resolved.