Last checked
Payment solutions for small businesses and enterprises to accept credit cards.
Experiencing an issue?

Propay está fora do ar?
Status unavailable
Share your experience to help others stay informed.
Status verification pending
The latest official observation is not fresh enough to confirm current service health.
Official provider statusOfficial incident active
ProPay Monthly Database Maintenance Reminder for July 2026 — At 3:00 a.m. (MT) on Thursday, July 16th, the database system will undergo its monthly maintenance. We anticipate no more than 5 minutes of service interruption during this time frame.
Official provider status0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 0m | Yes | Unknown | ||
| 43h 34m | Yes | Unknown | ||
| 28m | Yes | Unknown | ||
| 2533h 44mOngoing | Yes | Unknown | ||
| 66h 6m | Yes | Unknown | ||
| 4h 44m | Yes | Unknown | ||
| 71h 39m | Yes | Unknown | ||
| 3h 16m | Yes | Unknown |
O Uptimus monitora Propay pela fonte oficial e normaliza incidentes, manutenções e componentes em um status consistente.
Esta página inclui atualmente 15 componentes monitorados, 52 incidentes, 66 manutenções e 11 dias de histórico conhecido.
O Uptimus é um serviço independente e não é afiliado ao Propay. Um status saudável não garante que todos os usuários, dispositivos ou regiões estejam sem problemas.
Receba alertas quando Propay ou um componente monitorado informar uma falha grave ou crítica. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas. O histórico disponível contém 52 incidentes indexados e oferece contexto além do status atual. Um incidente recente indexado foi “Transaction Refund Issue - 10/7/26”.
Receba alertas sobre desempenho degradado, impacto parcial e incidentes que não representam uma falha completa. O Uptimus monitora atualmente 15 componentes do Propay: Direct Credit Card and ACH Processing, Integration TEST Environment, Websites, Mobile, and Card Readers, Payment Facilitation - Heartland, Portico. Os alertas podem ser enviados pelos canais ativados no workspace, incluindo e-mail, push e integrações configuradas.
Planned work published by the official provider.
As an update to our previously announced migration to a new ticketing system (https://status.propay.com/incidents/vktvqzb7zjmb) we wanted to provide this additional clarification. The new ticketing system has new, system-specific emails that have been created for our various ProPay teams, to help better route tickets to the various ProPay support groups. Moving forward, best practices will be to begin emailing these new emails to submit a ticket, when not logging in directly to submit a ticket. Please Note: Existing emails to the existing team emails will still function to create tickets, but those emails will be deprecated over the coming months, so please begin to transition to using the following emails: Existing Email: [email protected] New Email: [email protected] Existing Email: [email protected] New Email: [email protected] Existing Email: [email protected] New Email: [email protected] Existing Email: [email protected] New Email: [email protected] Existing Email: [email protected] Forward to: [email protected] Existing Email: [email protected] New Email: [email protected] Existing Email: [email protected] New Email: [email protected] Existing Email: [email protected] New Email: [email protected] Existing Email: [email protected] New Email: [email protected] Existing Email: [email protected] New Email: [email protected] Existing Email: [email protected] New Email: [email protected] Existing Email: [email protected] New Email: [email protected]
Started 1 Du 2026, 06:00 UTC · Ongoing
On Thursday, October 29th, between 00:00 and 05:00 (MT), ProPay will perform an upgrade to the production environment 26.PI19.R1 (October Release) *** All services and sites may be unavailable during this time frame. *** *We have added the “Authorized Signer First Name” and “Authorized Signer Last Name” fields to the Partner Portal to support enhanced merchant onboarding data quality and compliance requirements. This will show in the Account Overview section of the Partner Portal *We have corrected an issue with the TransType 34 API call, where transactions with insufficient funds were incorrectly returning ACHInReturned instead of ACHInRejected, causing downstream systems to misclassify failures and disrupt re-billing workflows. We have updated the TransType 34 response to return the correct status code. *We have added BusinessZipCode validation to ensure data integrity and compliance, as previous API updates for U.S. business accounts were accepting invalid ZIP code values due to missing validation. We have updated all API calls with a value to return an accurate response if the value is invalid. *We have improved the logic of the TransType 400 authorization API call to eliminate false Status 65 time out responses for transactions where payment authorizations succeeded. *We have updated the logic of the Comprehensive Risk Chargeback Report, due to an issue where the report displayed the representment status inconsistently across each daily report.. The update will prevent the issue where the same chargeback line could switch between New and Resolved on this report. With this update, a chargeback in arbitration should show New until it is resolved, and a resolved chargeback should show Resolved and keep the correct representment date.
Started 29 Here 2026, 06:00 UTC · Ongoing
The scheduled maintenance has been completed.
Started 12 Here 2026, 14:00 UTC · Resolved 14 Here 2026, 14:00 UTC
The scheduled maintenance has been completed.
Started 1 Here 2026, 06:00 UTC · Resolved 1 Here 2026, 06:05 UTC
The scheduled maintenance has been completed.
Started 1 Here 2026, 06:00 UTC · Resolved 1 Here 2026, 06:15 UTC
The scheduled maintenance has been completed.
Started 24 Gwen. 2026, 06:00 UTC · Resolved 24 Gwen. 2026, 11:00 UTC
The scheduled maintenance has been completed.
Started 24 Gwen. 2026, 06:00 UTC · Resolved 24 Gwen. 2026, 06:05 UTC
The scheduled maintenance has been completed.
Started 17 Gwen. 2026, 09:00 UTC · Resolved 17 Gwen. 2026, 09:05 UTC
As páginas públicas do Downdetector são orientadas por relatos de usuários. O Uptimus combina essa atividade com incidentes oficiais, manutenções e saúde dos componentes quando o provedor publica esses dados.
| Critérios de comparação | Uptimus | Downdetector |
|---|---|---|
| Relatos da comunidade sobre Propay | Incluído | Incluído |
| Linha de base adaptativa que separa casos isolados de uma interrupção ampla | Incluído | Incluído |
| Atividade de 24 horas e visualização regional de interrupções | Incluído | Incluído |
| Um espaço para sites, provedores de status, jogos Steam e apps e jogos Android | Incluído | Produto separado |
| Alertas por e-mail, push e webhook no mesmo espaço | Incluído | Produto separado |
| Atualizações oficiais de incidentes e linha do tempo de Propay | Incluído | Baseado em relatos |
| Saúde dos componentes e manutenções exibidas separadamente | Incluído | Limitado nas páginas públicas |
The current official status of Propay cannot be verified. The latest stored provider observation indicated normal operation. 0 reports were recorded for Propay in the last 24 hours. Last official check: .
Descubra outros serviços populares e seu status atual
Avalie este serviço
Ainda não há avaliações
Compartilhe sua opinião sobre Propay
Seja o primeiro a comentar!