Sticky incident

Issues with Authorize Payment API calls failing

Notice Resolved View vendor source →

Sticky experienced a notice incident on April 4, 2019 affecting Transaction API, lasting —. The incident has been resolved; the full update timeline is below.

Started
Apr 04, 2019, 04:27 PM UTC
Resolved
Apr 04, 2019, 04:27 PM UTC
Duration
—
Detected by Pingoru
Apr 04, 2019, 04:27 PM UTC

Affected components

Transaction API

Update timeline

  1. resolved Apr 04, 2019, 04:27 PM UTC

    Customers that use the authorize_payment https://developer-prod.limelightcrm.com/#f6c90e62-787f-4c21-ba49-ba52d9acdfda API method in their transaction flow or legacy 2 step web forms that perform $1 authorizations were experiencing failures from our Wednesday, April 3 release starting at 3:30pm ET through Thursday, April 4 at 11:40am ET. Error responses to the authorize_payment API call may have included erroneous messaging about attempting transactions against the auth.net payment gateway even when the client did not utilize that gateway in their CRM. The issue was caused by a code maintenance oversight introduced in our April 3 release. We have identified that 17 clients use authorize_payment API calls on a regular basis. Moving forward, we will be adding automated test cases for this use-case to prevent it from happening in the future. We apologize for any inconvenience this error may have caused.