Last checked
Payment solutions for small businesses and enterprises to accept credit cards.
Experiencing an issue?
Propay est-il en panne?
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 | ||
| 2534h 33mOngoing | Yes | Unknown | ||
| 66h 6m | Yes | Unknown | ||
| 4h 44m | Yes | Unknown | ||
| 71h 39m | Yes | Unknown | ||
| 3h 16m | Yes | Unknown |
Uptimus surveille Propay via sa source officielle et normalise les incidents, maintenances et composants en un état cohérent.
Cette page comprend actuellement 15 composants surveillés, 52 incidents, 66 maintenances et 11 jours d'historique connu.
Uptimus est un service indépendant sans affiliation avec Propay. Un état normal ne garantit pas que chaque utilisateur, appareil ou région soit épargné.
Recevez une alerte lorsque Propay ou un composant surveillé signale une panne majeure ou une perturbation critique. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées. L’historique disponible contient 52 incidents indexés, donnant à chaque alerte un contexte au-delà de l’état actuel. Un incident récent indexé était « Transaction Refund Issue - 10/7/26 ».
Recevez des alertes sur les performances dégradées, les impacts partiels et les incidents qui ne constituent pas une panne complète. Uptimus suit actuellement 15 composants Propay: Direct Credit Card and ACH Processing, Integration TEST Environment, Websites, Mobile, and Card Readers, Payment Facilitation - Heartland, Portico. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées.
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 nov. 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 oct. 2026, 06:00 UTC · Ongoing
The scheduled maintenance has been completed.
Started 12 oct. 2026, 14:00 UTC · Resolved 14 oct. 2026, 14:00 UTC
The scheduled maintenance has been completed.
Started 1 oct. 2026, 06:00 UTC · Resolved 1 oct. 2026, 06:05 UTC
The scheduled maintenance has been completed.
Started 1 oct. 2026, 06:00 UTC · Resolved 1 oct. 2026, 06:15 UTC
The scheduled maintenance has been completed.
Started 24 sept. 2026, 06:00 UTC · Resolved 24 sept. 2026, 11:00 UTC
The scheduled maintenance has been completed.
Started 24 sept. 2026, 06:00 UTC · Resolved 24 sept. 2026, 06:05 UTC
The scheduled maintenance has been completed.
Started 17 sept. 2026, 09:00 UTC · Resolved 17 sept. 2026, 09:05 UTC
Les pages publiques de Downdetector s’appuient surtout sur les signalements des utilisateurs. Uptimus les associe aux incidents officiels, maintenances et états des composants lorsque le fournisseur les publie.
| Critères de comparaison | Uptimus | Downdetector |
|---|---|---|
| Signalements communautaires concernant Propay | Inclus | Inclus |
| Référence adaptative distinguant les cas isolés d’une panne étendue | Inclus | Inclus |
| Activité des signalements sur 24 heures et vue régionale | Inclus | Inclus |
| Un espace pour les sites, pages de statut, jeux Steam et apps et jeux Android | Inclus | Produit séparé |
| Alertes e-mail, push et webhook depuis le même espace | Inclus | Produit séparé |
| Mises à jour officielles et chronologie du statut de Propay | Inclus | Piloté par les signalements |
| État des composants et maintenances affichés séparément | Inclus | Limité sur les pages publiques |
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: .
Partagez vos réflexions sur Propay
Soyez le premier à commenter!
Évaluez ce service
Aucun avis pour le moment
Découvrez d'autres services populaires et leur état actuel
