tag:status.wepay.com,2005:/historyWePay Status - Incident History2024-03-28T22:43:25-07:00WePaytag:status.wepay.com,2005:Incident/193697802023-12-07T12:37:38-08:002023-12-07T12:37:38-08:00Degraded Production Performance<p><small>Dec <var data-var='date'> 7</var>, <var data-var='time'>12:37</var> PST</small><br><strong>Resolved</strong> - Please be advised that the previously reported issue where some clients may have experienced degraded production performance has been resolved as of 3:13 PM ET.</p><p><small>Dec <var data-var='date'> 7</var>, <var data-var='time'>11:38</var> PST</small><br><strong>Investigating</strong> - Please be advised that we have detected an emerging issue where some clients are experiencing degraded production performance.<br /><br />Rest assured that we are actively addressing the issue and will publish an update as new information is available.</p>tag:status.wepay.com,2005:Incident/176192922023-06-19T09:23:59-07:002023-06-19T09:23:59-07:00POST /payments intermittent errors<p><small>Jun <var data-var='date'>19</var>, <var data-var='time'>09:23</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>19</var>, <var data-var='time'>04:21</var> PDT</small><br><strong>Monitoring</strong> - The issue has been identified and addressed. We are monitoring the issue.</p><p><small>Jun <var data-var='date'>19</var>, <var data-var='time'>04:12</var> PDT</small><br><strong>Identified</strong> - Wepay engineering is engaged and investigating the issue.</p>tag:status.wepay.com,2005:Incident/175968612023-06-15T09:00:00-07:002023-06-16T12:01:17-07:00V2 Hosted Hosted Checkout Flow Disruption on 6/15/23<p><small>Jun <var data-var='date'>15</var>, <var data-var='time'>09:00</var> PDT</small><br><strong>Resolved</strong> - On 6/15/23, between 11:55 AM - 6:58 PM PST, the V2 hosted checkout flow experienced a disruption. During this time, V2 hosted checkouts may have experienced an error in processing. All services were confirmed to be operational as of 6:58 PM PST.</p>tag:status.wepay.com,2005:Incident/175256032023-06-09T12:23:32-07:002023-06-09T12:23:54-07:00V2 and V3 API Outage earlier this afternoon<p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>12:23</var> PDT</small><br><strong>Resolved</strong> - WePay Engineers identified an incident earlier this afternoon which impacted the availability of the V2 and V3 APIs from 2PM ET to 2:10 PM ET. <br /><br />The incident was promptly investigated and the cause was identified. <br /><br />As of 2:10 PM ET, Service has been restored to normal for both V2 and V3 APIs.</p>tag:status.wepay.com,2005:Incident/169628722023-04-25T09:19:30-07:002023-04-25T09:19:30-07:00Elevated Error Rates Reported for V2 & V3 APIs<p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>09:19</var> PDT</small><br><strong>Resolved</strong> - V2 and V3 APIs are now operating as expected and service has been restored to normal.</p><p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>08:31</var> PDT</small><br><strong>Monitoring</strong> - WePay Engineers have identified the issue impacting the V2 and V2 APIs earlier this morning. <br /><br />Both V2 and V3 APIs are now operating normally.<br /><br />WePay Engineering Teams remain engaged and continue to monitor for stability.<br /><br />Further updated will be provided upon change of status.</p><p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>08:07</var> PDT</small><br><strong>Update</strong> - The WePay Engineering Team remain engaged and continue to investigate this incident. <br /><br />Further updates will be provided upon change of status.</p><p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>07:42</var> PDT</small><br><strong>Identified</strong> - Elevated Error Rates have been reported for V2 and V3 APIs. <br /><br />WePay Engineering Teams have been engaged and they are currently investigating this incident. <br /><br />Further updates will be provided upon change of status.</p>tag:status.wepay.com,2005:Incident/165493132023-03-17T14:03:09-07:002023-03-17T14:03:09-07:00E-Check and Card Not Present Authorization Failures Earlier this afternoon<p><small>Mar <var data-var='date'>17</var>, <var data-var='time'>14:03</var> PDT</small><br><strong>Resolved</strong> - Earlier this afternoon, at approximately 12:31 PT to 12:51 PT, there was a 20 minute authorization failure which impacted E-Check and Card Not Present transactions. The WePay Engineering Teams have resolved this incident. <br /><br />Partners experiencing issues during this time would need to retry any failed transactions, which was also communicated as part of the platform error messaging.</p>tag:status.wepay.com,2005:Incident/163336452023-03-03T17:17:19-08:002023-03-03T17:17:19-08:00Funding Delays for specific transactions<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>17:17</var> PST</small><br><strong>Resolved</strong> - The stuck withdrawals identified earlier today have now been resolved.<br /><br />Payouts will now happen as per their standard procedures.</p><p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>15:32</var> PST</small><br><strong>Update</strong> - The WePay Engineering continue to work to clear stuck withdrawals that were identified.<br /><br />Further updates to be provided upon change of status.</p><p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>13:39</var> PST</small><br><strong>Update</strong> - The WePay Engineering continue to work to clear stuck withdrawals that were identified.<br /><br />Further updates to be provided upon change of status.</p><p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>12:09</var> PST</small><br><strong>Update</strong> - The WePay Engineers have identified the root cause of this incident. <br /><br />The WePay Engineering continue to work to clear stuck withdrawals that were identified.<br /><br />Further updates to be provided upon change of status.</p><p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>10:38</var> PST</small><br><strong>Update</strong> - WePay Engineering Teams continue to work to clear stuck withdrawals that have been identified.<br /><br />Further updates to be provided upon change of status.</p><p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>09:58</var> PST</small><br><strong>Update</strong> - WePay Engineering Teams continue to work to clear stuck withdrawals that have been identified.<br /><br />Further updates to be provided upon change of status.</p><p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>09:01</var> PST</small><br><strong>Identified</strong> - The impact of this incident has been identified.<br /><br />WePay Engineering Teams are working to clear stuck withdrawals that have been identified.<br /><br />Further updates to be provided upon change of status.</p><p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>08:07</var> PST</small><br><strong>Update</strong> - WePay Engineering Teams remain engaged and continue to investigate this incident. <br /><br />Further updates to be provided upon change of status.</p><p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>07:14</var> PST</small><br><strong>Investigating</strong> - Beginning on 3/1, certain merchants are experiencing delayed funding for specific transactions. <br /><br />WePay Engineering Teams are actively investigating the issue to identify the root cause and address remediation.</p>tag:status.wepay.com,2005:Incident/162244802023-02-21T15:43:22-08:002023-02-21T15:43:22-08:00New V2 merchants are currently unable to complete the onboarding process<p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>15:43</var> PST</small><br><strong>Resolved</strong> - New V2 merchant onboarding process is now working as expected.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>15:27</var> PST</small><br><strong>Update</strong> - WePay Engineering Teams remain engaged and continue to investigate this issue with the highest priority.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>13:37</var> PST</small><br><strong>Update</strong> - WePay Engineering Teams remain engaged and continue to investigate this issue with the highest priority.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>12:03</var> PST</small><br><strong>Update</strong> - WePay Engineering Teams remain engaged and continue to investigate this issue with the highest priority.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>11:25</var> PST</small><br><strong>Update</strong> - WePay Engineering Teams remain engaged and continue to investigate this issue with the highest priority.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>10:46</var> PST</small><br><strong>Update</strong> - WePay Engineering Teams remain engaged and continue to investigate this issue with the highest priority.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>09:42</var> PST</small><br><strong>Investigating</strong> - New V2 merchants are currently unable to complete the onboarding process. WePay Engineering Teams have been engaged and they are currently investigating this issue with the highest priority.</p>tag:status.wepay.com,2005:Incident/160461232023-02-06T14:54:41-08:002023-02-06T14:54:47-08:00Degraded Approval Rates<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>14:54</var> PST</small><br><strong>Resolved</strong> - Discover has confirmed that the problem mentioned earlier in their environment has been resolved. <br /><br />At this time, all MOPs should be flowing normally including Discover.</p><p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>14:22</var> PST</small><br><strong>Monitoring</strong> - We are starting to see improvement in terms of authorizations and captures at this time. <br /><br />Discover has confirmed that the problem mentioned earlier in their environment has been addressed. <br /><br />At this time, other MOPs should be flowing normally.</p><p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>13:20</var> PST</small><br><strong>Investigating</strong> - We are currently experiencing issues obtaining timely responses from Discover for authorizations and captures. Engineering is actively engaged with Discover who has confirmed a problem in their environment that they are working with the highest priority to resolve. Until this issue is mitigated, platforms may experience increased latency for other MOPs (e.g., Visa, Mastercard, American Express) as well.</p>tag:status.wepay.com,2005:Incident/159760502023-01-30T13:40:49-08:002023-01-30T13:40:49-08:00Withdrawals not occurring as expected<p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>13:40</var> PST</small><br><strong>Resolved</strong> - Service has been restored to normal for the API response time issues reported earlier today.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>11:19</var> PST</small><br><strong>Monitoring</strong> - The higher API response times reported earlier have been resolved. <br /><br />The WePay Engineers remain engaged and continue to monitor the environment.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>09:39</var> PST</small><br><strong>Update</strong> - We are currently experiencing higher than normal response times for various API endpoints. <br /><br />WePay Engineering Teams remain engaged and they are actively investigating this issue with the highest priority.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>09:20</var> PST</small><br><strong>Identified</strong> - As of 10:50 AM ET, WePay Engineering Teams have identified the root cause of the issue and restarted merchant funding batches.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>08:49</var> PST</small><br><strong>Investigating</strong> - WePay Engineers have identified an issue impacting withdrawals. <br /><br />WePay Engineering Teams have been engaged and they are currently investigating this incident. <br /><br />Further updated to be provided upon change of status.</p>tag:status.wepay.com,2005:Incident/159153942023-01-24T07:36:45-08:002023-01-24T07:36:45-08:00V3 Payment Failures<p><small>Jan <var data-var='date'>24</var>, <var data-var='time'>07:36</var> PST</small><br><strong>Resolved</strong> - The cause of this incident has been identified, and the Engineering teams are making the required changes to prevent recurrence.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>16:03</var> PST</small><br><strong>Monitoring</strong> - WePay has identified the issue and has remediated. We will continue to monitor the systems affected.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>14:57</var> PST</small><br><strong>Update</strong> - Engineering teams remain engaged and continue to investigate this issue.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>13:22</var> PST</small><br><strong>Update</strong> - V2 Payment platforms are also experiencing elevated error rates. Customers should attempt to use their retry logic for errors that they experience at this time.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>12:37</var> PST</small><br><strong>Investigating</strong> - All calls for V3 payments are currently failing. Engineering teams have been engaged and they are currently investigating this issue.</p>tag:status.wepay.com,2005:Incident/146938802022-12-09T10:26:03-08:002022-12-09T10:26:03-08:00Merchant Center - Real Time Reporting Delays<p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>10:26</var> PST</small><br><strong>Resolved</strong> - Merchant Center continues to work as normal and real time reporting is working as expected.</p><p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>16:28</var> PST</small><br><strong>Monitoring</strong> - Merchant Center reporting delays have been resolved. Real Time data is now available within Merchant Center as normal. <br /><br />Support Teams will remain engaged and continue to monitor for stability.</p><p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>14:02</var> PST</small><br><strong>Investigating</strong> - We are currently experiencing an issue where real time reporting in Merchant Center is experiencing delays of up to 1 hour. We are investigating the cause of this issue and will provide updates as they are available.</p>tag:status.wepay.com,2005:Incident/141160092022-12-01T15:33:25-08:002022-12-01T15:33:25-08:00Elevated error rates reported on the V3 Post Payments Platform<p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>15:33</var> PST</small><br><strong>Resolved</strong> - The WePay Engineers identified the issue and it has been resolved. <br /><br />As of 2:34 PM PT, service has been restored to normal on the V3 Post Payment Platform.</p><p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>14:24</var> PST</small><br><strong>Investigating</strong> - WePay Engineers are currently investigating elevated error rates reported on the V3 Post Payments Platform.</p>tag:status.wepay.com,2005:Incident/132961762022-11-17T13:09:47-08:002022-11-17T13:09:47-08:00POST Terminal Endpoint Failures in PRD<p><small>Nov <var data-var='date'>17</var>, <var data-var='time'>13:09</var> PST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov <var data-var='date'>17</var>, <var data-var='time'>11:55</var> PST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Nov <var data-var='date'>17</var>, <var data-var='time'>11:42</var> PST</small><br><strong>Investigating</strong> - • At approx. 8:10a PST, high onboarding flow errors were detected<br />• Cause confirmed and under investigation<br />• Next update will be provided when more information has been made available to share</p>tag:status.wepay.com,2005:Incident/112206052022-09-22T08:59:07-07:002022-09-22T08:59:07-07:00V3 API Performance Degradation<p><small>Sep <var data-var='date'>22</var>, <var data-var='time'>08:59</var> PDT</small><br><strong>Resolved</strong> - The V3 API issue reported earlier this morning has been resolved. Service has been restored to normal.</p><p><small>Sep <var data-var='date'>22</var>, <var data-var='time'>07:12</var> PDT</small><br><strong>Monitoring</strong> - The V3 performance issues reported earlier have been mitigated. WePay technical teams will continue to monitor for stability.</p><p><small>Sep <var data-var='date'>22</var>, <var data-var='time'>06:33</var> PDT</small><br><strong>Identified</strong> - We have currently identified an issue impacting V3 API performance. WePay technical teams have been engaged and they are currently assessing this issue.</p>tag:status.wepay.com,2005:Incident/111506422022-09-16T08:44:47-07:002022-09-16T08:44:47-07:00Degraded performance across systems<p><small>Sep <var data-var='date'>16</var>, <var data-var='time'>08:44</var> PDT</small><br><strong>Resolved</strong> - System performance has been restored to normal.</p><p><small>Sep <var data-var='date'>16</var>, <var data-var='time'>03:41</var> PDT</small><br><strong>Monitoring</strong> - A fix has been made. System stats normal. We will continue to monitor.</p><p><small>Sep <var data-var='date'>16</var>, <var data-var='time'>02:46</var> PDT</small><br><strong>Update</strong> - We are continuing to work on a fix for the issue.</p><p><small>Sep <var data-var='date'>16</var>, <var data-var='time'>02:29</var> PDT</small><br><strong>Identified</strong> - Multiple systems impacted</p>tag:status.wepay.com,2005:Incident/107635712022-08-08T10:31:03-07:002022-08-08T10:31:03-07:00Production Elevated API Error Rates<p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>10:31</var> PDT</small><br><strong>Resolved</strong> - The technical teams have monitored throughout the weekend without any further issues. This incident is now closed.</p><p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>15:59</var> PDT</small><br><strong>Monitoring</strong> - We are seeing improved performance with our /account and /payments (V3)/checkouts (V2) endpoints as of 11 am PST (last spike) today after the instance of increased errors this morning. We will continue monitoring throughout the weekend to ensure no other degradation occurs.</p><p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>10:46</var> PDT</small><br><strong>Identified</strong> - We have identified a spike in API errors with our /account and /payments (V3)/checkouts (V2) endpoints. We are actively investigating and will provide an update shortly.</p><p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>21:04</var> PDT</small><br><strong>Monitoring</strong> - We are seeing improved performance with our /account and /payments (V3)/checkouts (V2) endpoints as of 5:31 pm PST. We will continue to monitor to ensure no other degradation takes place.</p><p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>17:57</var> PDT</small><br><strong>Investigating</strong> - We have identified a spike in API errors with our /account and /payments (V3)/checkouts (V2) endpoints. We are actively investigating and will provide an update shortly.</p>tag:status.wepay.com,2005:Incident/107743062022-08-06T16:20:58-07:002022-08-06T16:20:58-07:00Production Mobile card reader transactions Degraded performance<p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>16:20</var> PDT</small><br><strong>Resolved</strong> - We have continued to monitor the behavior of our services and are confident that there is no further disruption. This issue is resolved.</p><p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>15:08</var> PDT</small><br><strong>Monitoring</strong> - We have introduced a resolution for the errors being experienced. We are currently seeing API traffic flowing normally as of 2:45 PM PST. We will continue to closely monitor for any further disruption.</p><p><small>Aug <var data-var='date'> 6</var>, <var data-var='time'>14:23</var> PDT</small><br><strong>Investigating</strong> - We have identified an issue that is impacting mobile card reader transactions. Some merchants may have trouble connecting to card readers. Terminal and card not present transactions are successful and not impacted. We are investigating further at this time. We are actively in the process of resolving the issue and will continue to update.</p>tag:status.wepay.com,2005:Incident/105847932022-07-14T15:40:32-07:002022-07-14T15:45:38-07:00POST /payments capture outage<p><small>Jul <var data-var='date'>14</var>, <var data-var='time'>15:40</var> PDT</small><br><strong>Resolved</strong> - From approximately 3pm to 3:24pm WePay experienced an outage processing card present captures. Transactions should be able to be recaptured. The incident is resolved.</p>tag:status.wepay.com,2005:Incident/105036412022-07-11T05:56:36-07:002022-07-11T05:56:36-07:00Canadian network provider (Rogers) Service Interruption<p><small>Jul <var data-var='date'>11</var>, <var data-var='time'>05:56</var> PDT</small><br><strong>Resolved</strong> - The provider has informed us that service has been restored to normal as of July 9th at 10 PM ET.</p><p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>12:11</var> PDT</small><br><strong>Update</strong> - The provider continues their work to address the service interruption reported earlier today. There is currently no ETA on the repair but the provider reports that they are making progress. Further updates will be provided upon change of status.</p><p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>12:08</var> PDT</small><br><strong>Update</strong> - The provider continues their work to address the service interruption reported earlier today. There is currently no ETA on the repair but the provider reports that they are making progress. Further updates will be provided upon change of status.</p><p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>11:45</var> PDT</small><br><strong>Update</strong> - The provider’s technical teams remain engaged and are working to resolve the issue. Further updates will be provided upon change of status.</p><p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>08:41</var> PDT</small><br><strong>Monitoring</strong> - We’ve been informed that a Canadian network provider is experiencing a service interruption that has nationwide internet and cellular service impact across Canada. The provider’s technical teams remain engaged and are working to resolve the issue. Further updates will be provided upon change of status.</p>tag:status.wepay.com,2005:Incident/104361342022-06-29T15:07:30-07:002022-06-29T15:07:30-07:00Intermittent API Failures<p><small>Jun <var data-var='date'>29</var>, <var data-var='time'>15:07</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>29</var>, <var data-var='time'>09:08</var> PDT</small><br><strong>Update</strong> - There are no API failures since 7:30 AM PT<br /><br />We are currently seeing API traffic flowing normally. <br /><br />We will continue to closely monitor for any further disruption.</p><p><small>Jun <var data-var='date'>29</var>, <var data-var='time'>07:53</var> PDT</small><br><strong>Monitoring</strong> - We have identified an issue which is causing some API calls to intermittently fail.<br /><br />Resources are currently engaged to identify the root cause and remediate the issue.</p>tag:status.wepay.com,2005:Incident/103040992022-06-15T14:30:13-07:002022-06-15T14:30:13-07:00Production Elevated Card Present Authorization Errors<p><small>Jun <var data-var='date'>15</var>, <var data-var='time'>14:30</var> PDT</small><br><strong>Resolved</strong> - After additional review, we have identified no further disruption. This issue is resolved.</p><p><small>Jun <var data-var='date'>15</var>, <var data-var='time'>10:30</var> PDT</small><br><strong>Monitoring</strong> - We have confirmed that WePay Card Present transactions were not impacted at this time. We will continue to actively monitor to ensure no impact occurs.</p><p><small>Jun <var data-var='date'>15</var>, <var data-var='time'>09:57</var> PDT</small><br><strong>Update</strong> - We are continuing to investigate this issue and will provide more information as soon as possible.</p><p><small>Jun <var data-var='date'>15</var>, <var data-var='time'>09:35</var> PDT</small><br><strong>Investigating</strong> - We have identified an issue that is impacting some Card Present authorizations, we are investigating further at this time. During this period some card present authorizations may not successfully complete. We are actively in the process of resolving the issue and will continue to update.</p>tag:status.wepay.com,2005:Incident/102223692022-06-10T17:39:06-07:002022-06-10T17:39:06-07:00Production Elevated Card Present Authorization Errors<p><small>Jun <var data-var='date'>10</var>, <var data-var='time'>17:39</var> PDT</small><br><strong>Resolved</strong> - From 12:34 to 17:10 EDT today we experienced degraded authorization performance in our Card Present environment. During this period, Card Present merchants may have experienced elevated authorization failures. As of 17:11 EDT Card Present authorizations normalized within normal tolerances. We will continue to monitor this incident to confirm no other disruption occurs.</p><p><small>Jun <var data-var='date'>10</var>, <var data-var='time'>16:12</var> PDT</small><br><strong>Monitoring</strong> - At this time authorization error rates in the Card Present environment look stable and not operating outside of normal tolerances. Activity will continue to be monitored until this incident can be considered mitigated.</p><p><small>Jun <var data-var='date'>10</var>, <var data-var='time'>12:13</var> PDT</small><br><strong>Update</strong> - At this time we continue to see elevated error rates in our card-present environment. We see continued authorization success as we work through resolving the issue. Merchants will experience decreasing error rates during this period and we will provide additional information as it becomes available.</p><p><small>Jun <var data-var='date'>10</var>, <var data-var='time'>11:25</var> PDT</small><br><strong>Update</strong> - We are continuing to work to resolve the issue. We have confirmed that traffic is starting to normalize and the error rate is dropping. We are continuing to monitor the behavior at this time.</p><p><small>Jun <var data-var='date'>10</var>, <var data-var='time'>10:41</var> PDT</small><br><strong>Identified</strong> - We have identified an issue which is impacting some Card Present authorizations and are investigating further at this time. During this time some card present authorizations may not successfully complete. We are actively in the process of resolving the issue and will continue to update.</p>tag:status.wepay.com,2005:Incident/100465012022-05-21T11:30:00-07:002022-05-21T15:23:44-07:00Production: Elevated Card Present Errors<p><small>May <var data-var='date'>21</var>, <var data-var='time'>11:30</var> PDT</small><br><strong>Resolved</strong> - Between 11:40am - 12:47pm PT, WePay identified an elevated error rate for card present transactions. During this period some card-present authorizations may have been impacted and unable to be successfully authorized. We have confirmed that all authorizations are operating normally at this time.</p>tag:status.wepay.com,2005:Incident/99540472022-05-09T19:01:00-07:002022-05-09T19:01:00-07:00Stage Outage- V3 APIs<p><small>May <var data-var='date'> 9</var>, <var data-var='time'>19:01</var> PDT</small><br><strong>Resolved</strong> - We have continued to monitor the behavior of our services and are confident that there is no further disruption. This issue is resolved.</p><p><small>May <var data-var='date'> 9</var>, <var data-var='time'>18:38</var> PDT</small><br><strong>Monitoring</strong> - We have introduced a resolution for the errors being experienced. We are currently seeing API traffic flowing normally as of 6.35 PM PT. We will continue to closely monitor for any further disruption.</p><p><small>May <var data-var='date'> 9</var>, <var data-var='time'>18:17</var> PDT</small><br><strong>Identified</strong> - We have identified the issue and are in the process of working to resolve as quickly as possible. We apologize for any impact you are currently experiencing. We will continue to provide updates until resolved.</p><p><small>May <var data-var='date'> 9</var>, <var data-var='time'>18:07</var> PDT</small><br><strong>Investigating</strong> - We are experiencing a disruption to our Stage server functionality. During this time V3 APIs with in our stage environment may have intermittent failures. We are in the process of investigating the occurrence and will provide additional details shortly.</p>