Authorize.net

Affected: Authorize.net API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-09-13 04:05 UTC

   Authorize.net is aware of an issue that is currently affecting Authorize.net API services and has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 09/13/2026, 02:07 GMT Reported End Time:...

2. postmortem 2026-09-17 09:05 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-11996)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Authorize.net API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-07 10:44 UTC

   Authorize.net is aware of an issue that is currently affecting the Authorize.net API Service. We are investigating the cause and working urgently to resolve the issue. Impact: Clients may experience errors or delays when sending or receiving API requests, which could impact...

2. monitoring 2026-09-07 12:39 UTC

   A fix has been implemented, and we are monitoring closely to ensure the issue is resolved. Impact: The issue has been mitigated, and customers are now able to use the Authorize.net API Service as expected. Reported Start Time: 05 September 2026, 12:37 GMT Reported End Time: 07...

3. resolved 2026-09-08 09:07 UTC

   The issue affecting the Authorize.net API Service has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 05 September 2026, 12:37 GMT Reported End Time: 07 September 2026, 12:12 GMT Impact:...

4. postmortem 2026-09-11 04:56 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link: [Post Incident Report ](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-11820)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Customer Invoicing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-02 15:43 UTC

   Authorize.net is aware of an issue that is currently affecting Customer Invoicing services. We are investigating the cause and working urgently to resolve the issue. Impact: Users may be experiencing issues where paid invoices are not updating to a "Paid" status. Reported Start...

2. monitoring 2026-09-02 16:52 UTC

   We have identified the issue affecting Customer Invoicing services and implemented a fix. We are closely monitoring to ensure the issue is resolved. Impact: Customer Invoicing processing has returned to normal. Reported Start Time: 01 September 2026, 01:00 GMT Next Update:...

3. resolved 2026-09-02 18:12 UTC

   The issue affecting Authorize.net’s Customer Invoicing services has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 01 September 2026, 01:00 GMT Reported End Time: 02 September 2026, 16:45...

4. postmortem 2026-09-04 11:34 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-11756)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Server Integration Method (SIM)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-20 15:13 UTC

   Authorize.net is aware of an issue that is currently affecting the Server Integration Method (SIM) Relay Response. We are investigating an issue where some customers may encounter a blank page after successful payment submission, and we are working urgently to resolve the issue....

2. investigating 2026-08-20 15:16 UTC

   Authorize.net is aware of an issue that is currently affecting the Server Integration Method (SIM) Relay Response. We are investigating an issue where some customers may encounter a blank page after successful payment submission, and we are working urgently to resolve the issue....

3. identified 2026-08-20 16:12 UTC

   Authorize.net has identified the issue affecting the Server Integration Method (SIM) Relay Response and we appreciate your patience as we work urgently to implement a mitigation. Impact: Merchants using SIM Relay Response may experience an issue where customers are redirected to...

4. resolved 2026-08-21 20:47 UTC

   The issue affecting Server Integration Method (SIM) Relay Response Service has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 01 July 2026, 12:00 GMT Reported End Time: 21 August 2026,...

5. postmortem 2026-08-24 21:39 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: API Connection/Endpoints

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-15 05:25 UTC

   Authorize.net is aware of an issue that is currently affecting the Hosted Payment form service in Sandbox Environment. We are investigating the cause and working urgently to resolve the issue. Impact: Merchants may experience issues completing payments through Sandbox hosted...

2. resolved 2026-08-15 07:11 UTC

   The issue affecting the Hosted Payment Form Service in Sandbox Environment has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 12 August 2026 3:00 PM GMT Reported End Time: 15 August 2026...

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Accept Suite

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-14 20:42 UTC

   Authorize.net is aware of an issue that is currently affecting the Hosted Payment form service. We are investigating the cause and working urgently to resolve the issue. Impact: Merchants may experience issues completing payments through hosted payment forms due to a CAPTCHA...

2. resolved 2026-08-15 04:37 UTC

   The issue affecting the Hosted Payment Form Service has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 12 August 2026 3:00 PM GMT Reported End Time: 15 August 2026 3:15 AM GMT Impact:...

3. postmortem 2026-08-17 22:49 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: NAB EPX

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-13 17:32 UTC

   Authorize.net is aware of an issue that is currently affecting the NAB Processor transaction processing. We have received confirmation from NABEPX that they are aware of the issue on their end and we are actively communicating with them to identify and resolve the issue. Impact:...

2. monitoring 2026-08-13 18:18 UTC

   The issue affecting transactions processed through the NABEPX processor has been mitigated. Visa continues to monitor closely with NABEPX to confirm service stability and ensure the issue is fully resolved. Impact: Merchants may have encountered transactions returning RTC 20 on...

3. resolved 2026-08-14 19:13 UTC

   The issue affecting NABEPX transaction processing has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Impact: Merchants are now able to process transactions on NABEPX processor as normal. Reported Start Time:...

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Simple Checkout

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-11 23:09 UTC

   Authorize.net is aware of an issue that is currently affecting Simple Checkout processing. We are investigating the cause and working urgently to resolve the issue. Impact: Clients using Simple Checkout may see unexpected processing volumes. Reported Start Time: 03 August 2026,...

2. investigating 2026-08-13 19:25 UTC

   Authorize.net continues to investigate the cause and working urgently to resolve the issue. For the time being, users are advised to enable Advanced Fraud Detection Suite filters to identify any suspicious transaction activity with a filter action of Do Not Authorize and Hold...

3. monitoring 2026-08-20 19:01 UTC

   Authorize.net has implemented backend changes to mitigate the issue affecting the Simple Checkout service. We are continuing to monitor the Simple Checkout service for discrepancies and will provide updates until the issue has been resolved. Impact: The issue has been mitigated...

4. resolved 2026-09-22 11:57 UTC

   The issue affecting Simple Checkout services has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 03 August 2026, 21:14 GMT Reported End Time: 20 August 2026, 19:00 GMT Impact: Customers...

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Vantiv

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-08 18:19 UTC

   Authorize.net is aware of an issue that is currently affecting Vantiv transaction processing. We are investigating the cause and working urgently to resolve the issue. Impact: Users may experience delays, intermittent errors, or transaction failures for payment-related services....

2. investigating 2026-08-08 22:33 UTC

   Authorize.net continues to investigate the issue that is currently affecting Vantiv transaction processing. Impact: Users may experience delays, intermittent errors, or transaction failures for payment-related services. Reported Start Time: 03 August 2026, 21:14 GMT Next Update:...

3. monitoring 2026-08-09 03:18 UTC

   A fix has been implemented for the issue affecting Vantiv transaction processing and we are monitoring closely to ensure the issue is resolved. Impact: The issue impacting Vantiv transaction processing has been mitigated. Reported Start Time: 21:14 GMT on August 03, 2026...

4. resolved 2026-08-09 04:59 UTC

   The issue affecting Vantiv transaction processing has now been fully resolved. Reported Start Time: 21:14 GMT on August 03, 2026 Reported End Time: 01:15 GMT on August 09, 2026 Impact: Users are now able to use Vantiv transaction processing as normal. Next Update: No further...

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Corporate Site, Support Center

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-23 18:11 UTC

   Authorize.net is aware of an issue that is currently affecting the functionality of Corporate and Support Web Sites. We are investigating the cause and working urgently to resolve the issue. We regret any inconvenience this may cause for our customers. We will provide regular...

2. resolved 2026-07-23 21:28 UTC

   The issue affecting the functionality of Corporate and Support Web Sites has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 13:30 GMT, 23 July 2026 Reported End Time: 19:15 GMT, 23 July...

3. postmortem 2026-07-30 12:33 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-11451)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Merchant Interface/Portal, Access/Login - Mobile Point of Sale (mPOS), Access/Login - Partner Interface/Portal, Access/Login - Windows App

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-12 03:42 UTC

   Authorize.net is aware of an issue that is currently affecting the login process for Merchant and/or Partner Interface. We are investigating the cause and working urgently to resolve the issue. Impact: Users may experience issues with login for Merchant and/or Partner Interface....

2. investigating 2026-07-12 04:08 UTC

   After further investigation, more impact had been identified. This include mPOS and Windows App. We are investigating the cause and working urgently to resolve the issue. Impact: Users may experience issues with login for Mulitples Portal Interface. Reported Start Time: July...

3. identified 2026-07-12 04:27 UTC

   Partial recovery has been done and mPOS and Windows App is working as expected. We have identified the issue affecting the issue of the Merchant and Partner Interface. We appreciate your patience as we work urgently to implement a mitigation. Impact: Users may experience login...

4. monitoring 2026-07-12 05:02 UTC

   The issue affecting multiple portal Interface has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: July 12th, 2:15 AM GMT Impact: Customers are now able to use all relevant portal Interface...

5. resolved 2026-07-12 06:21 UTC

   The issue affecting multiple portal Interface has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: July 12th, 2:15 AM GMT Reported End Time: July 12th 04:13 AM GMT Impact: Customers are now...

6. postmortem 2026-08-04 22:46 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following [link](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-11463).

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Transaction Management/Search - Merchant Interface/Portal

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-03 16:05 UTC

   Authorize.net was made aware of an issue that affected the transaction management for Merchant Interface/Portal. The issue has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 03 July 2026,...

2. postmortem 2026-07-07 20:42 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following [link](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-11369).

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Vantiv

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-30 14:41 UTC

   Authorize.net is aware of an issue that is currently affecting Vantiv refund settlement processing. We are investigating the cause and working urgently to resolve the issue. Impact: This issue is impacting the settlement of refund transactions processed through Vantiv. Reported...

2. investigating 2026-06-30 14:43 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-07-01 14:52 UTC

   A fix has been implemented and we are monitoring closely to ensure the issue is fully resolved. Impact: This issue impacted the settlement of refund transactions processed through Vantiv. Reported Start Time: 24 June 2026 06:42 GMT Reported End Time: 1 July 2026 03:10 GMT Next...

4. resolved 2026-07-06 01:53 UTC

   The issue affecting the Vantiv refund settlement processing has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 24 June 2026 06:42 GMT Reported End Time: 1 July 2026 03:10 GMT Impact:...

5. postmortem 2026-07-06 03:33 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link: [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-11360)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Portals

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-19 01:35 UTC

   Authorize.net is aware of an issue that is currently affecting the login process for Sandbox and Partner Login. We are investigating the cause and working urgently to resolve the issue. Impact: There is an issue with the Sandbox login where users are unable to log in after...

2. resolved 2026-06-19 03:21 UTC

   The issue affecting the Sandbox and Partner Login has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 21:42 GMT on 06/18/2026 Reported End Time: 01:36 GMT on 06/19/2026 Impact: Users are...

3. postmortem 2026-06-22 20:57 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following [link.](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-11256)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Authorize.net API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-04 10:37 UTC

   Authorize.net is aware of an issue that is currently affecting Authorize.net API. We are investigating the cause and working urgently to resolve the issue. Impact: Users may experience issues with Authorize.net API connectivity. Reported Start Time: 04 June 2026, TBD Next...

2. investigating 2026-06-04 11:43 UTC

   Authorize.net is aware of an issue that is currently affecting some Authorize.Net API transactions. We are investigating the cause and working urgently to resolve the issue. Impact: Users may experience issues with some API transactions returning an invalid response code....

3. monitoring 2026-06-04 12:24 UTC

   A fix has been implemented and we are monitoring closely to ensure the issue is resolved. Impact: The issue has been mitigated and Authorize.Net API transactions are now working as expected. Reported Start Time: 04 June 2026, 05:50 GMT Reported End Time: 04 June 2026, 11:56 GMT...

4. resolved 2026-06-04 17:30 UTC

   Correction The issue affecting the some Authorize.Net API transactions has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 04 June 2026 5:50 GMT Reported End Time: 04 June 2026 11:40 GMT...

5. postmortem 2026-06-09 11:33 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-10757)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Global Payments North America (GPN)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-05-22 04:19 UTC

   Authorize.net was aware of an issue that affected settlement/batching for Global Payments North America (GPN). The issue has been mitigated. We are monitoring closely to ensure the issue is resolved. Impact: Customers may have experienced funding settlement issues. Reported...

2. resolved 2026-05-22 06:35 UTC

   The issue affecting settlement/batching for Global Payments North America (GPN) has now been fully resolved. No SLA had been missed due to this incident. Reported Start Time: 05/21/2026 Reported End Time: 05/22/2026 Impact: The issue impacting settlement funding has been fully...

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Vantiv

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-13 13:56 UTC

   Authorize.net is aware of a service disruption currently preventing certain transactions from being processed. Impact: This may impact some Visa cardholders' ability to make payments. We are investigating the cause and working urgently to resolve the situation. Reported Start...

2. resolved 2026-05-13 14:59 UTC

   The issue that prevented certain transactions from being processed has now been fully resolved. Authorize.Net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 13 May 2026, 08:47 GMT Reported End Time: 13 May 2026, 14:38 GMT...

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Merchant Interface/Portal, Access/Login - Partner Interface/Portal

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-09 10:49 UTC

   Authorize.net is aware of a service disruption. We are in the initial stages of investigation and will share more information as soon as possible. We regret any inconvenience this may cause for our customers.

2. investigating 2026-05-09 10:51 UTC

   Authorize.net is aware of an issue that is currently affecting the login process for Merchant and Partner Interfaces We are investigating the cause and working urgently to resolve the issue. Impact: Users may experience issues with login for Merchant and Partner Interfaces....

3. monitoring 2026-05-09 11:02 UTC

   A fix has been implemented and we are monitoring closely to ensure the issue is resolved. Impact: The issue has been mitigated and customers are now able to use the Merchant and Partner Interface as expected. Reported Start Time: 9 May 2026 09:03 GMT Reported End Time: 9 May...

4. resolved 2026-05-09 15:05 UTC

   The issue affecting the Merchant and Partner Interface has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 9 May 2026 09:03 GMT Reported End Time: 9 May 2026 10:52 GMT Impact: Customers...

5. postmortem 2026-05-15 12:43 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following [Link](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-10678).

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Developer Center

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-05 09:23 UTC

   Authorize.net is aware of an issue that is currently affecting Sandbox Account creation process. Users may receive an error message stating: “The sandbox is experiencing technical difficulties. Please try to create a test account in a few minutes.” We are investigating the cause...

2. resolved 2026-05-05 13:43 UTC

   The issue affecting the Sandbox Account creation process has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 05 May 2026, 07:57 GMT Reported End Time: 05 May 2026, 12:34 GMT Impact: Users...

3. postmortem 2026-05-05 23:29 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-10486)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Accept Suite

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-26 04:30 UTC

   Authorize.net is aware of an issue that is currently affecting transaction processing using Accept Suite API services. We are investigating the cause and working urgently to resolve the issue. Reported Start Time: 8:00 AM GMT on 25 April 2026 Impact: Users may experience OTS...

2. monitoring 2026-04-26 05:40 UTC

   We have identified the issue, a fix has been implemented, and we are monitoring closely to ensure the issue is resolved. Reported Start Time: 8:00 AM GMT on 25 April 2026 Impact: Users may have experienced OTS Token errors when transactions were created using Accept Suite API....

3. resolved 2026-04-26 10:01 UTC

   The issue affecting the Accept Suite API services has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 25 April 2026 07:35 GMT Reported End Time: 26 April 2026 02:27 GMT Impact: Customers...

4. postmortem 2026-05-15 11:43 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following [Link](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-10677).

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Merchant Interface/Portal

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-20 07:34 UTC

   Authorize.net is aware of an issue that is currently affecting the Ask ANET tool for Merchant Interface. We are investigating the cause and working urgently to resolve the issue. Impact: Users may experience issues with the Ask ANET for Merchant Interface. Reported Start Time:...

2. identified 2026-04-20 08:36 UTC

   Authorize.net continues to work urgently to resolve the issue that is currently affecting the Ask ANET tool for Merchant Interface. Impact: Users may experience issues with the Ask ANET for Merchant Interface. Reported Start Time: 18 April 2026 08:19 GMT Next Update: When...

3. identified 2026-04-20 10:16 UTC

   Authorize.net remains working urgently to resolve the issue that is currently affecting the Ask ANET tool for Merchant Interface. Impact: Users may experience issues with the Ask ANET for Merchant Interface. Reported Start Time: 17 April 2026. 22:19 GMT Next Update: When Current...

4. identified 2026-04-20 21:25 UTC

   Authorize.net teams continue with their efforts to resolve the issue that is currently affecting the Ask ANET tool for Merchant Interface. Impact: Users may experience issues with the Ask ANET for Merchant Interface. Reported Start Time: 17 April 2026. 22:19 GMT Next Update:...

5. resolved 2026-04-21 05:14 UTC

   The issue affecting the Ask ANET tool for Merchant Interface has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 17 April 2026. 22:19 GMT Reported End Time: 21 April 2026. 00:58 GMT...

6. postmortem 2026-04-24 13:55 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link [here](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-10557)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Authorize.net API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-10 22:26 UTC

   Authorize.net is aware of a service disruption currently preventing certain transactions from being processed. We are investigating the cause and working urgently to resolve the situation. We are investigating the cause and working urgently to resolve the issue. Impact:...

2. investigating 2026-04-10 23:10 UTC

   Authorize.net is aware of a service disruption currently preventing certain transactions from being processed. We continue investigating the cause and working urgently to resolve the situation. Impact: Merchants may be experiencing a rise in customers being unable to complete...

3. identified 2026-04-10 23:31 UTC

   We have identified the issue affecting the performance of the Authorize.API Impact: Merchants may be experiencing a rise in customers being unable to complete their transactions, which could result in an increased number of abandoned purchases. Reported Start Time: 10 April 2026...

4. monitoring 2026-04-11 01:28 UTC

   A fix has been implemented, and we are monitoring closely to ensure the issue is resolved. Impact: The issue has been mitigated and customers are now able to use the API as expected. Reported Start Time: 10 April 2026 at 20:15 GMT Next Update: As current status changes. Please...

5. resolved 2026-04-11 01:53 UTC

   The issue affecting the Authorize.net API has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 10 April 2026 at 20:15 GMT Reported End Time: 11 April 2026 at 00:15 GMT Impact: customers are...

6. postmortem 2026-04-14 09:44 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link [Post Incident Report.](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-10497)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Webhooks

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-08 15:03 UTC

   Authorize.net is aware of an issue that is currently affecting some Transaction Details on Webhooks Payment Event where certain details are missing. We were able to reproduce the issue and confirmed that the missing fields are as follows: 1. Correct response code 2. Amount 3....

2. identified 2026-04-08 17:25 UTC

   We have identified the issue affecting some Transaction Details on Webhooks Payment Event where certain details are missing. We appreciate your patience as we work urgently to implement a mitigation. Impact: Merchants may notice that certain details are missing from webhook...

3. resolved 2026-04-08 19:20 UTC

   The issue affecting some Transaction Details on Webhooks Payment Event has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 7 April 2026 at 20:00 GMT Reported End Time: 8 April 2026 at...

4. postmortem 2026-04-09 08:25 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link [here](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-10480)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Portals

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-08 03:14 UTC

   Authorize.net is aware of an issue that is currently affecting the Sandbox Account creation process. We are investigating the cause and working urgently to resolve the issue. Impact: Users may experience issues while creating Sandbox Account. Reported Start Time: 3:19 PM GMT on...

2. investigating 2026-04-08 04:14 UTC

   We continue to investigate the cause and working urgently to resolve the issue that is currently affecting the Sandbox Account creation process. Impact: Users may experience issues while creating Sandbox Account. Reported Start Time: 3:19 PM GMT on 7 April 2026 Next Update: As...

3. resolved 2026-04-08 14:40 UTC

   The issue affecting the Sandbox Account creation process has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 7 April 2026 15:19 GMT Reported End Time: 8 April 2026 13:40 GMT Impact:...

4. postmortem 2026-04-09 21:49 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-10486)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Authorize.net API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-27 00:03 UTC

   Authorize.net is aware of an issue that is currently affecting the Merchant email receipts. We are investigating the cause and working urgently to resolve the issue. Impact: Users may experience missing information in the Merchant Email receipts. Reported Start Time: 25 March...

2. investigating 2026-03-27 00:58 UTC

   We continue to investigate the issue affecting the Merchant email receipts, and we appreciate your patience as we work urgently to implement a mitigation. Impact: Users may experience missing information in the Merchant Email receipts. Reported Start Time: 25 March 2026 Next...

3. identified 2026-03-27 01:48 UTC

   We have identified the issue affecting the Merchant Email receipts, and we appreciate your patience as we work urgently to implement a mitigation. Impact: Users may experience missing information in the Merchant Email receipts. Reported Start Time: 25 March 2026 Next Update: As...

4. resolved 2026-03-27 08:10 UTC

   The issue affecting the Merchant Email receipts has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 25 March 2026 15:30 GMT Reported End Time: 26 March 2026 04:40 GMT Impact: Customers are...

5. postmortem 2026-03-30 17:52 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link: [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-10403)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Virtual Terminal

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-25 12:48 UTC

   Authorize.net is aware of an issue that is currently affecting customer transactions. We have identified the cause and working urgently to resolve the issue. Impact: Authorize only transactions are being processed as authorized and captured which may result in funds being...

2. identified 2026-03-25 13:50 UTC

   We are continuing to work on a fix for this issue. Impact: Authorize only transactions are being processed as authorized and captured which may result in funds being transferred from customer accounts without prior notification. Reported Start Time: 23 March 2026 Next Update:...

3. resolved 2026-03-25 14:10 UTC

   The issue affecting Processing transactions in Accept Payments in MINT 2.0 has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 23 March 2026 14:00 GMT Reported End Time: 25 March 2026...

4. postmortem 2026-03-26 11:00 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link [Here](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-10392)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: API Connection/Endpoints

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-13 21:14 UTC

   Authorize.net is aware of a service disruption affecting the Sandbox environment. Webhook notifications may be delayed or not be sent as expected. Use of the transaction reporting API during this time is recommended. We apologize for any inconvenience this may have caused. We...

2. investigating 2026-03-13 22:26 UTC

   Authorize.net continues to investigate the service disruption affecting the Sandbox environment. Webhook notifications may be delayed or not be sent as expected. Use of the transaction reporting API during this time is recommended. We apologize for any inconvenience this may...

3. resolved 2026-03-14 00:23 UTC

   The issue affecting the Sandbox environment has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 13 March 2026 Reported End Time: 00:00 GMT on 14 March 2026 Impact: Customers are now able...

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Add/Manage Merchant - Partner Interface/Portal

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-12 19:12 UTC

   We are performing proactive maintenance within the Authorize.Net 2.0 interface. As part of this work, the ability to edit other users in the 2.0 interface is temporarily restricted. Adding users, deleting users, and editing your own profile information remain available and...

2. identified 2026-03-12 20:11 UTC

   Teams continue to perform proactive maintenance within the Authorize.Net 2.0 interface, temporarily restricting the ability to edit other users in the 2.0 interface. Adding users, deleting users, and editing your own profile information remain available and unaffected. We are...

3. resolved 2026-03-12 21:09 UTC

   The issue affecting the Authorize.Net 2.0 Interface has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 12 March 2026 at 18:15 GMT Reported End Time: 12 March 2026 at 22:47 GMT Impact:...

4. postmortem 2026-03-17 17:34 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link: [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-10315)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Merchant Interface/Portal

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-26 16:42 UTC

   Authorize.net is aware of an issue that is currently affecting the login process for Merchant Interface. We are investigating the cause and working urgently to resolve the issue. Impact: Users may experience issues with login for Merchant Interface. Reported Start Time: 26...

2. monitoring 2026-02-26 17:33 UTC

   A fix has been implemented and we are monitoring closely to ensure the issue is resolved. Impact: The issue has been mitigated and customers are now able to use the Merchant Interface as expected. Reported Start Time: 26 February 2026 at 16:20 GMT Reported End Time: 26 February...

3. resolved 2026-02-26 21:42 UTC

   The issue affecting the Merchant Interface has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 26 February 2026 at 16:20 GMT Reported End Time: 26 February 2026 at 20:49 GMT Impact:...

4. postmortem 2026-02-27 08:11 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-10147)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Portals, Reports - Merchant Interface/Portal

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-02-12 22:09 UTC

   Authorize.net became aware of an issue that affected the Merchant Interface (MINT) when merchants attempted to download transaction reports. A fix has been implemented, and we are monitoring closely to ensure the issue is resolved. Impact: Users may have received the error:...

2. resolved 2026-02-13 00:02 UTC

   The issue affecting the Merchant Interface has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 12 February 2026 at 19:30 GMT Reported End Time: 12 February 2026 at 21:56 GMT Impact:...

3. postmortem 2026-02-13 23:24 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link: [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-10084)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Merchant Interface/Portal

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-28 20:13 UTC

   Authorize.net is aware of an issue that is currently affecting the login process for Merchant Interface. Users may receive the following error, "We encountered an error. Please try again. If this error continues, contact Merchant Support." We are investigating the cause and...

2. investigating 2026-01-28 21:13 UTC

   Authorize.net continues to investigate the issue affecting the login process for Merchant Interface. Users may receive the following error, "We encountered an error. Please try again. If this error continues, contact Merchant Support." We are working urgently to resolve the...

3. identified 2026-01-28 22:41 UTC

   We have identified the issue affecting the login process for Merchant Interface. We appreciate your patience as we work urgently to implement a mitigation. Impact: Users may experience issues with login for Merchant Interface. Reported Start Time: 19:00 GMT 28 January 2026 Next...

4. identified 2026-01-28 23:57 UTC

   We appreciate your patience as we continue to work urgently to implement a mitigation. Impact: Users may experience issues with login for Merchant Interface. Reported Start Time: 19:00 GMT 28 January 2026 Next Update: As status changes or additional information is provided. We...

5. resolved 2026-01-29 03:09 UTC

   The issue affecting the Merchant Interface has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 19:00 GMT, 28 January 2026 Reported End Time: 02:54 GMT, 29 January 2026 Impact: Customers...

6. postmortem 2026-01-30 04:04 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-09953)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Merchant Interface/Portal

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-22 20:49 UTC

   Authorize.net is aware of an issue that is currently affecting the login process for MINT and One Time Password (OTP) PIN validation. Users can select SMS for PIN delivery until mitigation. We are investigating the cause and working urgently to resolve the issue. Impact: Users...

2. identified 2026-01-22 21:47 UTC

   We have identified the issue affecting the performance of the Merchant Interface is related to an ongoing vendor outage. Our team is actively working with vendor to resolve the email delivery problem. Impact: Users may experience issues with Login and OTP delivery via email for...

3. resolved 2026-01-23 07:20 UTC

   The issue affecting the Merchant Interface and One Time Password (OTP) PIN validation has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 20:01 GMT , 22 January 2026 Reported End Time:...

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Portals

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-20 22:51 UTC

   Authorize.net is aware of an issue that is currently affecting developer.authorize.net. Some clients may experience an error when attempting to create a Sandbox account. We are investigating the cause and working urgently to resolve the issue. Impact: Users may experience issues...

2. investigating 2026-01-20 23:45 UTC

   Authorize.net is aware of an issue that is currently affecting developer.authorize.net. Some clients may experience an error when attempting to create a Sandbox account. We continue investigating the cause and working urgently to resolve the issue. Impact: Users may experience...

3. resolved 2026-01-26 20:25 UTC

   The issue affecting Sandbox account creation via developer.authorize.net has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 16:00 GMT on 20 January 2026 Reported End Time: 14:10 GMT on 24...

4. postmortem 2026-01-27 23:32 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-09916)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Merchant Interface/Portal, Access/Login - Partner Interface/Portal

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-08 18:52 UTC

   Authorize.net is aware of an issue that is currently affecting the performance for Merchant and/or Partner Interface. We are investigating the cause and working urgently to resolve the issue. Impact: Users may experience issues with login for Merchant and/or Partner Interface,...

2. investigating 2026-01-08 19:50 UTC

   Authorize.net continues to investigate the issue that is currently affecting the performance of the Merchant and/or Partner Interface. We are working urgently to resolve the issue and greatly appreciate your patience during this time. Impact: Users may experience issues with...

3. monitoring 2026-01-09 00:00 UTC

   A fix has been implemented, and we are monitoring closely to ensure the issue is resolved. Impact: The issue has been mitigated, and customers are now able to use the Merchant and Partner Interface as expected. Users may have experienced issues with login for Merchant and/or...

4. resolved 2026-01-12 23:04 UTC

   The issue affecting the Merchant and Partner Interface has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 15:45 GMT 8 January 2026 Reported End Time: 23:48 GMT 8 January 2026 Impact:...

5. postmortem 2026-01-19 03:55 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-09826)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Merchant Interface/Portal, Access/Login - Partner Interface/Portal

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-12 20:49 UTC

   Authorize.net is aware of an issue that is currently affecting the performance for Merchant and/or Partner Interface. We are investigating the cause and working urgently to resolve the issue. Impact: Users may experience latency for Merchant and/or Partner Interface. There is no...

2. investigating 2025-12-12 21:39 UTC

   Authorize.net continues to investigate the issue currently affecting the performance for Merchant and/or Partner Interface. We are working urgently to resolve the issue and appreciate your patience. Impact: Users may experience latency for Merchant and/or Partner Interface....

3. investigating 2025-12-12 22:35 UTC

   We appreciate your patience as we continue to work urgently to resolve the issue. Impact: Users may experience latency for Merchant and/or Partner Interface. There is no impact to transaction processing. Reported Start Time: 12 December 2025 Next Update: As status changes or...

4. monitoring 2025-12-12 23:54 UTC

   A fix has been implemented and we are monitoring closely to ensure the issue is resolved. Impact: The issue has been mitigated and customers are now able to use the Merchant and Partner Interface as expected. Reported Start Time: 12 December 2025 Reported End Time: 23:30 GMT 12...

5. monitoring 2025-12-15 12:50 UTC

   The issue affecting the Merchant and Partner Interface has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 12 December 2025 18:15 GMT Reported End Time: 12 December 2025 23:30 GMT Impact:...

6. resolved 2025-12-15 13:13 UTC

   The issue affecting the Merchant and Partner Interface has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 12 December 2025 18:15 GMT Reported End Time: 12 December 2025 23:30 GMT Impact:...

7. postmortem 2025-12-19 18:01 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-09757)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Merchant Interface/Portal

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-19 18:51 UTC

   Authorize.net is aware of an issue that is currently affecting Merchant Interface (MINT) which may be preventing clients from managing their user profile or adding new users to their gateway account. As a workaround, any account which has been enabled for MINT 2.0 can toggle...

2. resolved 2025-11-19 19:21 UTC

   The issue affecting the Merchant Interface has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 9:05 GMT 19 November 2025 Reported End Time: 20:04 GMT 19 November 2025 Impact: Customers are...

3. postmortem 2025-11-21 04:45 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-09623)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Merchant Interface/Portal, Access/Login - Partner Interface/Portal

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-18 13:49 UTC

   Authorize.net is aware of an issue that is currently affecting MINT access We are investigating the cause and working urgently to resolve the issue. Impact: Users may experience issues with MINT portal access Reported Start Time: 18 November 2025 Next Update: Within 60 minutes...

2. identified 2025-11-18 14:30 UTC

   We have identified the issue affecting the performance of Authorize.net Portals and we appreciate your patience as we work urgently on mitigation. Impact: Users may experience issues with Authorize.net portals. Reported Start Time: Next Update: As current status changes We...

3. monitoring 2025-11-18 14:50 UTC

   A fix has been implemented and we are monitoring closely to ensure the issue is resolved. Impact: The issue has been mitigated and customers are now able to use the Merchant and Partner Portals as expected. Reported Start Time: 18 November 2025 13:20 GMT Reported End Time: 18...

4. resolved 2025-11-18 15:43 UTC

   The issue affecting the Merchant and Partner Interface has now been fully resolved. Reported Start Time: 18 November 2025 13:20 GMT Reported End Time: 18 November 2025 14:35 GMT Impact: Customers are now able to use the Merchant and Partner Interface as normal. Next Update: No...

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Heartland Payment Systems

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-10 16:22 UTC

   Authorize.net is aware that a Financial Ecosystem Participant is experiencing a service disruption that may be impacting some cardholders ability to make payments. Visa’s systems continue to operate normally and no issues have been identified within VisaNet that could be...

2. investigating 2025-11-10 16:49 UTC

   Authorize.net is aware of a service disruption currently preventing certain transactions from being processed. We regret any inconvenience this may cause for our customers. We will provide regular updates until the issue is mitigated. Impact: This may impact some Visa...

3. investigating 2025-11-10 17:45 UTC

   Authorize.net is aware of a service disruption currently preventing certain transactions from being processed. We regret any inconvenience this may cause for our customers. We will continue to provide updates until the issue is mitigated. Impact: This may impact some Visa...

4. resolved 2025-11-10 21:21 UTC

   The issue affecting Payment Gateway Processing for certain customers has now been fully resolved. Reported Start Time: 10 November 2025 at 14:21 GMT Reported End Time: 10 November 2025 at 17:50 GMT Impact: Customers may now process payments as expected. Next Update: No further...

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Merchant Interface/Portal, Access/Login - Partner Interface/Portal

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-05 06:01 UTC

   Authorize.net is aware of an issue that is currently affecting the login process for Merchant and/or Partner Interface. We are investigating the cause and working urgently to resolve the issue. Impact: Users may experience issues with login for Merchant and/or Partner Interface....

2. monitoring 2025-11-05 06:06 UTC

   A fix has been implemented and we are monitoring closely to ensure the issue is resolved. Impact: The issue has been mitigated and customers are now able to use the Merchant and Partner Interface as expected. Next Update: As current status changes. Please do not hesitate to...

3. resolved 2025-11-05 08:13 UTC

   The issue affecting the Merchant and Partner Interface has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 05:24 GMT on 5 November 2025 Reported End Time: 06:00 GMT on 5 November 2025...

4. postmortem 2025-11-06 10:34 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following [link. ](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-09550)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Mobile Point of Sale (mPOS)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-23 15:09 UTC

   Authorize.net is currently aware of an issue impacting the 2.0 Mobile App on iOS, where users encounter the error message: "Log in failed. An unexpected error occurred. Please try again later.” Authorize.net is investigating the cause and working urgently to resolve the issue....

2. investigating 2025-09-23 16:03 UTC

   We continue to investigate the issue impacting the 2.0 Mobile App on iOS, where users encounter the error message: "Log in failed. An unexpected error occurred. Please try again later.” We appreciate your patience as we work urgently to implement a mitigation. Impact: Users may...

3. investigating 2025-09-23 17:59 UTC

   We appreciate your patience as we work towards mitigating the issue impacting the 2.0 Mobile App on iOS. Some affected users may be able to login via biometrics. Impact: Users may experience issues with mPOS 2.0 login. Affected users are encouraged to attempt login via...

4. monitoring 2025-09-23 21:41 UTC

   A fix has been implemented, and we are monitoring closely to ensure the issue is resolved. Impact: Users should no longer have issues with mPOS 2.0 login. Reported Start Time: 22 September 2025, 23:00 GMT Reported End Time: 23 September 2025, 21:20 GMT Next Update: As current...

5. resolved 2025-09-24 21:49 UTC

   The issue has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Impact: Users should no longer have issues with mPOS 2.0 login. Reported Start Time: 22 September 2025, 23:00 GMT Reported End Time: 23 September...

6. postmortem 2025-09-24 21:53 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link [Post Incident...

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Corporate Site

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-16 08:14 UTC

   Cybersource is aware of an issue that is currently affecting the functionality of https://demo.authorize.net/ We are investigating the cause and working urgently to resolve the issue. Impact: Users are unable to access https://demo.authorize.net/ Reported Start Time: 16 August...

2. monitoring 2025-08-16 08:31 UTC

   A fix has been implemented and we are monitoring closely to ensure the issue is resolved. Impact: The issue has been mitigated and customers are now able to use https://demo.authorize.net/ as expected. Reported Start Time: 16 August 2025 05:40 GMT Reported End Time: 16 August...

3. resolved 2025-08-16 10:33 UTC

   The issue affecting https://demo.authorize.net/ has now been fully resolved. Cybersource is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 16 August 2025 05:40 GMT Reported End Time: 16 August 2025 08:12 GMT Impact: Customers are...

4. postmortem 2025-08-18 03:05 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-08946)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Accept Suite, Authorize.net API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-12 19:36 UTC

   Authorize.net is aware of an issue which is affecting transaction processing resulting in error E00001 responses being sent for successful transactions. The issue is currently ongoing, and we are investigating the root cause. Impact: Users may have received response codes...

2. monitoring 2025-08-12 20:18 UTC

   A fix has been implemented and we are monitoring closely to ensure the issue is resolved. Impact: The issue has been mitigated and customers should no longer receive the response code E00001 for transactions that are successfully processing. Reported Start Time: 17:00 GMT on 6...

3. resolved 2025-08-13 00:09 UTC

   The issue affecting transaction responses has been resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 17:00 GMT on 6 August 2025 Reported End Time: 20:00 GMT on 12 August 2025 Impact: The response code is...

4. postmortem 2025-08-13 20:25 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Merchant Interface/Portal, Access/Login - Partner Interface/Portal

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-08-06 06:23 UTC

   Authorize.net was aware of an issue which affected the access for merchants and/or partners using new.authorize.net and demo.authorize.net. The issue has been resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Impact: Users may...

2. postmortem 2025-08-06 22:07 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Merchant Interface/Portal

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-03 20:45 UTC

   Authorize.net is aware of an issue that is currently affecting the activation process for Merchant Interface. We are investigating the cause and working urgently to resolve the issue. Impact: New merchants may be experiencing issues activating their account. Reported Start Time:...

2. investigating 2025-06-03 21:54 UTC

   Authorize.net is aware of an issue affecting the activation process for Merchant Interface. We appreciate your patience as we continue to work urgently to resolve the issue. Impact: New merchants may be experiencing issues activating their account. Reported Start Time: 3 June...

3. monitoring 2025-06-04 01:33 UTC

   We have identified and fixed the issue affecting the account activation process and users who encountered issues while activating their account should now be able to activate their account without any issue. We continue to monitor the situation closely to ensure it is resolved....

4. resolved 2025-06-04 20:50 UTC

   The issue that affected the activation process for Merchant Interface has now been resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 30 May 2025 Reported End Time: 4 June 2025 at 01:10 GMT Impact: New...

5. postmortem 2025-06-05 15:17 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-08442)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: TSYS Acquiring Solutions

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-03 10:01 UTC

   Authorize.net is aware of an issue that is currently affecting settlement/batching for TSYS. We are investigating the cause and working urgently to resolve the issue. Impact: Customers may experience funding settlement issues. Reported Start Time: 3 June 2025 05:22 GMT Next...

2. investigating 2025-06-03 10:52 UTC

   Authorize.net continues to investigate the issue that is currently affecting settlement/batching for TSYS. Impact: Customers may experience funding settlement issues. Reported Start Time: 3 June 2025 05:22 GMT Next Update: Within 60 minutes We regret any inconvenience this may...

3. resolved 2025-06-03 12:34 UTC

   The issue affecting settlement/batching notification for TSYS has now been fully resolved. Authorize.net are conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 3 June 2025 05:22 GMT Reported End Time: 3 June 2025 12:18 GMT Impact:...

4. postmortem 2025-06-05 06:45 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-08440)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Merchant Interface/Portal, Access/Login - Partner Interface/Portal

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-02 20:36 UTC

   Authorize.net is aware of a service disruption affecting the delivery of SMS PINs. This appears to be isolated to phone numbers on the T-Mobile network. There is no impact to email PIN delivery, therefore clients should be able to access their account by selecting Email PIN...

2. investigating 2025-06-03 01:17 UTC

   We are continuing our investigation and will share more information as soon as possible. We regret any inconvenience this may cause for our customers. Impact: Users may be unable to receive SMS PINs when requesting from phone numbers on the T-Mobile network. Reported Start Time:...

3. investigating 2025-06-03 10:52 UTC

   Summary: We are continuing our investigations and will share more information as soon as possible. Only SMS PIN delivery is impacted. There is no impact to email PIN delivery, therefore clients should be able to access their account by selecting Email PIN instead of SMS PIN when...

4. monitoring 2025-06-03 15:51 UTC

   A fix has been implemented and we are monitoring closely to ensure the issue is resolved. Impact: The issue has been mitigated and clients on the T-Mobile network are now able to receive SMS PINs. Reported Start Time: 19 May 2025 Mitigated: 3 June 2025 Next Update: As current...

5. resolved 2025-06-04 21:14 UTC

   The issue affecting the delivery of SMS PINs for Merchant and Partner Interfaces has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences Reported Start Time: 19 May 2025 Mitigated: 3 June 2025 Impact: The issue has...

6. postmortem 2025-06-04 21:21 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link: [Post Incident Report]( https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-08439)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: AIB Merchant Services (AIBMS), American Express Direct, Barclays Merchant Services, Cardnet, Chase Paymentech Solutions, eCheck/ACH, Elavon, EVO, FdiAus, First Data Nashville, First Data Omaha, Global Payments North America (GPN), HBOS, Heartland Payment Systems, Worldpay, HSBC, NAB EPX, Streamline, TSYS Acquiring Solutions, Vantiv, WestPac

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-05-09 14:44 UTC

   Authorize.net was aware of an issue that may have impacted transaction processing for merchants. This issue is currently mitigated, and we are working urgently to confirm the issue is fully resolved. Impact: Users may have experienced issues with processing transactions....

2. resolved 2025-05-09 15:38 UTC

   The issue affecting the transaction processing for merchants has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Impact: Customers are now able to process transactions normally. Reported Start Time: 9 May 2025...

3. postmortem 2025-05-09 21:45 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link, [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-08346)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Reports - Merchant Interface/Portal

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-03-03 17:26 UTC

   Authorize.net is aware of an issue that is currently affecting the account users from receiving Merchant Transaction Receipts. We are investigating the cause and working urgently to resolve the issue. Start Time: ~23:30 GMT on 28 February 2025 Next Update: The next update will...

2. resolved 2025-03-03 21:28 UTC

   The issue affecting the account users from receiving Merchant Transaction Receipts has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: ~23:30 GMT on 28 February 2025 Reported End Time:...

3. postmortem 2025-03-06 18:23 UTC

   Clients and merchants can access the Post Incident Report with their Support Center login credentials at the following link. [Post Incident Report](https://support.authorize.net/knowledgebase/Knowledgearticle/?code=KA-07983)

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: Access/Login - Merchant Interface/Portal

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-02-20 23:50 UTC

   Transaction email receipts in Test Mode are currently unavailable. We are continuing to work to restore full access. We appreciate your patience as we work urgently to resolve the issue. Impact: Transaction email receipts in Test Mode are currently unavailable. Reported Start...

2. monitoring 2025-02-25 01:10 UTC

   The transaction email receipts in Test Mode are now re-enabled. We are monitoring to confirm the issue is fully resolved. Impact: Transaction email receipts in Test Mode are now available. Start: 20 February 2025 End: 23:50 GMT 24 February 2025 Next Update: Only if there are any...

3. resolved 2025-02-26 00:37 UTC

   The issue affecting the transaction email receipts in Test Mode has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 20 February 2025 Reported End Time: 23:50 GMT 24 February 2025 Impact:...

Excerpts are shortened. Read the full incident on Authorize.net's status page.

Affected: EVO

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-02-20 16:38 UTC

   An issue that was affecting EVO transaction processing has been mitigated. We are monitoring to confirm the issue is fully resolved. Impact: Users may have experienced payment processing errors with certain transactions. Reported Start Time: 16:31 GMT - 20 February 2025 Next...

2. monitoring 2025-02-20 16:45 UTC

   An issue that was affecting EVO transaction processing has been mitigated. We are monitoring to confirm the issue is fully resolved. Impact: Users may have experienced payment processing errors with EVO SNAP transactions. Reported Start Time: 13:16 GMT - 20 February 2025 Next...

3. resolved 2025-02-21 01:09 UTC

   The issue affecting EVO Processor has now been fully resolved. Authorize.net is conducting an internal review of the events to mitigate future occurrences. Reported Start Time: 15:16 GMT - 20 February 2025 Reported End Time: 17:04 GMT - 20 February 2025 Impact: Customers are now...

Excerpts are shortened. Read the full incident on Authorize.net's status page.