All Systems Operational

About This Site

Current System Status:-

Advanced Fraud Detection Suite (AFDS) Operational
API End Points Operational
Automated Recurring Billing (ARB) Operational
Customer Information Manager (CIM) Operational
Settlement/Batching Operational
Credit Cards Operational
eCheck.Net/ACH Operational
Transaction Processing Operational
Credit Cards Operational
eCheck.Net/ACH Operational
Merchant Interface (MINT) Operational
Access/Login Operational
Reports/Transaction Search Operational
Batch/File Upload Operational
Partner Interface (PINT) Operational
Access/Login Operational
Reporting Operational
Virtual Point of Sale (VPOS) Operational
Access/Login Operational
Sandbox Environment ? Operational
Corporate Web Sites Operational
Developer Center - https://developer.authorize.net/ Operational
Corporate Site - https://www.authorize.net/ Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
The legacy Virtual Point of Sale (VPOS) v1 application (https://anet.vpos.authorize.net/) is being replaced with Virtual Point of Sale (VPOS) v2 (https://vpos2.authorize.net) and VPOS v1 url will be redirected to the VPOS v2 url/system and in the future removed.

Any Authorize.Net merchant can now use the new Virtual Point of Sale (VPOS) v2 (https://vpos2.authorize.net) to processes retail transactions using a supported card reader purchased through our partner POS Portal. Instructions on how to install and use VPOS v2 can be found here (https://support.authorize.net/s/article/VPOS-version-2-FAQ).

To help with the migration from legacy VPOS v1 to VPOS v2 Authorize.Net will be redirecting VPOS v1 traffic to the new VPOS v2 url and system on the following dates and times:

• Temporary redirect (rescheduled): 08/21/2019 from 10:00am PT to 12:00pm PT
• Final redirect: 08/28/2019 @ 10:00am PT – from this point forward only VPOS v2 will be available.

For more information on the replacement and end of life of VPOS v1 please see support article: Legacy Virtual Point of Sale EOL and Upgrade to new Virtual Point of Sale (https://support.authorize.net/s/article/Legacy-Virtual-Point-of-Sale-EOL-and-Upgrade-to-new-Virtual-Point-of-Sale).
Posted on Aug 14, 10:43 PDT
The legacy Virtual Point of Sale (VPOS) v1 application (https://anet.vpos.authorize.net/) is being replaced with Virtual Point of Sale (VPOS) v2 (https://vpos2.authorize.net) and VPOS v1 url will be redirected to the VPOS v2 url/system and in the future removed.

Any Authorize.Net merchant can now use the new Virtual Point of Sale (VPOS) v2 (https://vpos2.authorize.net) to processes retail transactions using a supported card reader purchased through our partner POS Portal. Instructions on how to install and use VPOS v2 can be found here (https://support.authorize.net/s/article/VPOS-version-2-FAQ).

To help with the migration from legacy VPOS v1 to VPOS v2 Authorize.Net will be redirecting VPOS v1 traffic to the new VPOS v2 url and system on the following dates and times:

• Final redirect: 08/28/2019 @ 10:00am PT – from this point forward only VPOS v2 will be available.

For more information on the replacement and end of life of VPOS v1 please see support article: Legacy Virtual Point of Sale EOL and Upgrade to new Virtual Point of Sale (https://support.authorize.net/s/article/Legacy-Virtual-Point-of-Sale-EOL-and-Upgrade-to-new-Virtual-Point-of-Sale).
Posted on Aug 5, 13:15 PDT
Past Incidents
Aug 19, 2019

No incidents reported today.

Aug 18, 2019

No incidents reported.

Aug 17, 2019

No incidents reported.

Aug 16, 2019

No incidents reported.

Aug 15, 2019
Completed - Scheduled maintenance has been completed. For more information on managing your relay response url please see the support article: SIM Relay Response Basics & Whitelisting (https://support.authorize.net/s/article/SIM-Relay-Response-Basics) and How do I add or delete Relay or Response URLs? (https://support.authorize.net/s/article/How-do-I-add-or-delete-Relay-or-Response-URLs).
Aug 15, 12:43 PDT
In progress - Scheduled maintenance has started. We will update once the change has been fully completed.
Aug 15, 09:39 PDT
Scheduled - Authorize.Net is enhancing security with our hosted payment form (Server Integration Method (SIM) (https://developer.authorize.net/api/upgrade_guide/#sim) or Direct Post Method (DPM)) (https://developer.authorize.net/api/upgrade_guide/#dpm) with Relay Response and white listing what url(s) can be used with this integration method.

On 08/15/2019 we plan on enhancing the white listing for Relay Response and requiring the Relay Response url(s) to be listed and if not reject the request with Response Code 14 (https://developer.authorize.net/api/reference/responseCodes.html?code=14) and prevent the payment form from loading successfully. This is to enhance security for both merchants and customers. As a part of this change we will be changing the check of the full url to just the domain is matching with any Relay Response url(s) passed in the API call. To help with this Authorize.Net will be adding domains we see used on merchants for the month of June 2019 to their accounts settings to help prevent any issues with this update.

To prevent any impact with the coming change merchants will need to add any Relay Response url(s) or domain(s) their solution/integration uses to the Merchant Interface and Relay/Receipt Urls settings. For steps on this process please see the support article: SIM Relay Response Basics & Whitelisting (https://support.authorize.net/s/article/SIM-Relay-Response-Basics) and How do I add or delete Relay or Response URLs? (https://support.authorize.net/s/article/How-do-I-add-or-delete-Relay-or-Response-URLs)
Aug 8, 08:00 PDT
Aug 14, 2019
Completed - The maintenance and redirect has been stopped and rolled back as there was an issue with the change. We will be rescheduling this temporary redirect for 08/21/2019 for the same time (10:00am PT to 12:00pm PT).
Aug 14, 10:40 PDT
In progress - Scheduled maintenance has started. Traffic from Virtual Point of Sale (VPOS) v1 application (https://anet.vpos.authorize.net/) will be redirected to Virtual Point of Sale (VPOS) v2 (https://vpos2.authorize.net).
Aug 14, 10:03 PDT
Scheduled - The legacy Virtual Point of Sale (VPOS) v1 application (https://anet.vpos.authorize.net/) is being replaced with Virtual Point of Sale (VPOS) v2 (https://vpos2.authorize.net) and VPOS v1 url will be redirected to the VPOS v2 url/system and in the future removed.

Any Authorize.Net merchant can now use the new Virtual Point of Sale (VPOS) v2 (https://vpos2.authorize.net) to processes retail transactions using a supported card reader purchased through our partner POS Portal. Instructions on how to install and use VPOS v2 can be found here (https://support.authorize.net/s/article/VPOS-version-2-FAQ).

To help with the migration from legacy VPOS v1 to VPOS v2 Authorize.Net will be redirecting VPOS v1 traffic to the new VPOS v2 url and system on the following dates and times:

• Temporary redirect: 08/14/2019 from 10:00am PT to 12:00pm PT
• Final redirect: 08/28/2019 @ 10:00am PT – from this point forward only VPOS v2 will be available.

For more information on the replacement and end of life of VPOS v1 please see support article: Legacy Virtual Point of Sale EOL and Upgrade to new Virtual Point of Sale (https://support.authorize.net/s/article/Legacy-Virtual-Point-of-Sale-EOL-and-Upgrade-to-new-Virtual-Point-of-Sale).
Aug 5, 13:12 PDT
Aug 13, 2019

No incidents reported.

Aug 12, 2019

No incidents reported.

Aug 11, 2019

No incidents reported.

Aug 10, 2019

No incidents reported.

Aug 9, 2019
Resolved - This incident has been resolved.
Aug 9, 10:16 PDT
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 9, 09:38 PDT
Update - We are currently still troubleshooting the issue. At this time, we have no estimated time frame for when a resolution will be in place.
Aug 9, 09:17 PDT
Investigating - We are aware of an issue that is currently affecting the Automated Recurring Billing (ARB) service for some merchants. We are working to resolve the issue as quickly as possible and apologize for any disruption.
Aug 9, 08:18 PDT
Aug 8, 2019

No incidents reported.

Aug 7, 2019

No incidents reported.

Aug 6, 2019

No incidents reported.

Aug 5, 2019

No incidents reported.