Last checked
Payment solutions for small businesses and enterprises to accept credit cards.
Experiencing an issue?
Czy Propay nie działa?
Degraded performance
Share your experience to help others stay informed.
Official status checked
Propay is experiencing issues
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 | ||
| 2535hOngoing | Yes | Unknown | ||
| 66h 6m | Yes | Unknown | ||
| 4h 44m | Yes | Unknown | ||
| 71h 39m | Yes | Unknown | ||
| 3h 16m | Yes | Unknown |
Uptimus monitoruje Propay przez oficjalne źródło i normalizuje incydenty, konserwacje oraz komponenty do jednego spójnego statusu.
Strona zawiera obecnie 15 komponentów, 52 incydentów, 66 konserwacji i 11 dni znanej historii.
Uptimus jest niezależny i nie jest powiązany z Propay. Prawidłowy status nie gwarantuje braku problemów u każdego użytkownika, urządzenia lub regionu.
Otrzymuj alerty, gdy Propay lub monitorowany komponent zgłasza poważną albo krytyczną awarię. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje. Dostępna historia zawiera 52 incydentów i zapewnia kontekst wykraczający poza bieżący status. Ostatni zarejestrowany incydent to „Transaction Refund Issue - 10/7/26”.
Otrzymuj alerty o obniżonej wydajności, częściowym wpływie i mniejszych incydentach. Uptimus monitoruje obecnie 15 komponentów Propay: Direct Credit Card and ACH Processing, Integration TEST Environment, Websites, Mobile, and Card Readers, Payment Facilitation - Heartland, Portico. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje.
Podziel się swoimi przemyśleniami na temat Propay
Bądź pierwszą osobą, która skomentuje!
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 lis 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 paź 2026, 06:00 UTC · Ongoing
The scheduled maintenance has been completed.
Started 12 paź 2026, 14:00 UTC · Resolved 14 paź 2026, 14:00 UTC
The scheduled maintenance has been completed.
Started 1 paź 2026, 06:00 UTC · Resolved 1 paź 2026, 06:15 UTC
The scheduled maintenance has been completed.
Started 1 paź 2026, 06:00 UTC · Resolved 1 paź 2026, 06:05 UTC
The scheduled maintenance has been completed.
Started 24 wrz 2026, 06:00 UTC · Resolved 24 wrz 2026, 11:00 UTC
The scheduled maintenance has been completed.
Started 24 wrz 2026, 06:00 UTC · Resolved 24 wrz 2026, 06:05 UTC
The scheduled maintenance has been completed.
Started 17 wrz 2026, 09:00 UTC · Resolved 17 wrz 2026, 09:05 UTC
Publiczne strony Downdetector opierają się głównie na zgłoszeniach użytkowników. Uptimus łączy je z oficjalnymi incydentami, pracami serwisowymi i stanem komponentów, gdy dostawca je publikuje.
| Kryteria porównania | Uptimus | Downdetector |
|---|---|---|
| Zgłoszenia społeczności dotyczące Propay | Dostępne | Dostępne |
| Adaptacyjna baza odróżniająca pojedyncze zgłoszenia od większej awarii | Dostępne | Dostępne |
| Aktywność z 24 godzin i regionalna mapa awarii | Dostępne | Dostępne |
| Jeden obszar dla stron, dostawców statusu, gier Steam oraz aplikacji i gier Android | Dostępne | Oddzielny produkt |
| Alerty e-mail, push i webhook z tego samego obszaru | Dostępne | Oddzielny produkt |
| Oficjalne aktualizacje i historia statusu Propay | Dostępne | Oparte na zgłoszeniach |
| Stan komponentów i prace serwisowe pokazane osobno | Dostępne | Ograniczone publicznie |
The official status page for Propay reports normal operation. An unresolved official incident is listed: “ProPay Monthly Database Maintenance Reminder for July 2026”. 0 reports were recorded for Propay in the last 24 hours. Last official check: .
Oceń tę usługę
Brak recenzji
Odkryj inne popularne usługi i ich aktualny stan
