Localpayment status
Localpayment status history
- Operational
- Degraded
- Partial outage
- Major outage
- Community report
Community reports
No community reports yet
No users have reported issues with this provider yet.
Official incidents
in the last 30 days
-
3rd Party Apparent Incident for Payout in Peru
We would like to inform that we are currently observing an issue from one of our third-party providers affecting Payout transactions in Peru.
Customers may experience increased errors or delays when processing transactions.
Our team has already contacted the provider and is awaiting confirmation and further details about the impact.
We will share additional updates as soon as more information becomes available.
All Localpayment services are fully operational.
If you have any questions or need assistance please contact our support team at support@localpayment.com
Kindly Regards,
Localpayment.
We would like to inform that the issue affecting Payout transactions in Peru has been identified as originating from one of our third-party providers.
The provider has acknowledged the situation and is working on applying the necessary corrective actions to restore normal operation.
Our team continues to monitor the impact and will share further updates as soon as more information becomes available.
All Localpayment services are fully operational.
If you have any questions or need assistance please contact our support team at support@localpayment.com
Kindly Regards,
Localpayment.
This incident has been resolved. -
3rd Party External Incident for Payout in Mexico
We would like to inform that a subset of Payout transactions in Mexico is currently experiencing a delay in their processing due to an issue identified on the side of one of our third-party providers.
Transactions continue to be received normally, but some Payouts may remain pending for longer than usual. The provider has acknowledged the situation and is applying the necessary corrective actions, which are expected to be completed during the next business day. In the meantime, our team is actively monitoring and processing pending transactions to minimize the impact.
We will share further updates as soon as more information becomes available.
All other Localpayment services remain fully operational.
If you have any questions or need assistance please contact our support team at support@localpayment.com
Kindly Regards,
Localpayment.
We would like to inform that our third-party provider has implemented corrective actions, and we are already observing improvements in transaction performance.
Our team continues to monitor the situation in coordination with the provider to ensure full stability before marking the incident as resolved.
We will share further updates if any new developments occur.
All LocalPayment services are fully operational.
Kindly Regards,
LocalPayment.
This incident has been resolved. -
3rd Party External Incident for Payout in Argentina
We would like to inform that Payout transactions in Argentina are currently experiencing a delay in their approval.
Transactions continue to be received normally, but their approval may take longer than usual. All pending Payouts will be processed as soon as regular operation is restored.
Our team is actively working to normalize approval times and will share further updates as soon as more information becomes available.
All other Localpayment services remain fully operational.
If you have any questions or need assistance please contact our support team at support@localpayment.com
Kind regards,
Localpayment.
This incident has been resolved. -
3rd Party Apparent Incident for Payout in Brazil
We would like to inform that we are currently observing an issue from one of our third-party providers affecting Payout transactions in Brazil.
Customers may experience increased errors or delays when processing transactions.
Our team has already contacted the provider and is awaiting confirmation and further details about the impact.
We will share additional updates as soon as more information becomes available.
All Localpayment services are fully operational.
If you have any questions or need assistance please contact our support team at support@localpayment.com
Kindly Regards,
Localpayment.
We would like to inform that our third-party provider has implemented corrective actions, and we are already observing improvements in transaction performance.
Our team continues to monitor the situation in coordination with the provider to ensure full stability before marking the incident as resolved.
We will share further updates if any new developments occur.
All LocalPayment services are fully operational.
Kindly Regards,
LocalPayment.
This incident has been resolved.
Services
No currently affected Localpayment services
-
PayIn APIs
Operational -
PayOut APIs
Operational -
LocalPayment V3
Operational -
STAGE
Operational -
PayIn Argentina
Operational -
PayOut Argentina
Operational -
PayIn Bolivia
Operational -
PayOut Bolivia
Operational -
PayIn Brazil
Operational -
PayOut Brazil
Operational -
PayIn Chile
Operational -
PayOut Chile
Operational -
PayIn Colombia
Operational -
PayOut Colombia
Operational -
PayIn Costa Rica
Operational -
PayOut Costa Rica
Operational -
PayIn Dominican Republic
Operational -
PayOut Dominican Republic
Operational -
PayIn Guatemala
Operational -
PayOut Guatemala
Operational -
PayIn Honduras
Operational -
PayOut Honduras
Operational -
PayIn Mexico
Operational -
PayOut Mexico
Operational -
VIrtual Accounts
Operational -
PayIn Panama
Operational -
PayOut Panama
Operational -
PayIn Paraguay
Operational -
PayOut Paraguay
Operational -
PayIn Peru
Operational -
PayOut Peru
Operational -
Cloud Infrastructure (AWS)
Operational
About Localpayment status page
- Monitoring since Oct 2026
- 32 services and components tracked
- 54 incidents total
- Last updated: Oct 25, 2026
Saw an error in description or reports for Localpayment?
Frequently asked questions
Quick answers for payment teams and merchants investigating an incident. Firemap explains the evidence; it does not diagnose your merchant account.
No. Localpayment reports normal operation on its official status page. Firemap last read the status page today at 15:08 UTC.
They are the four status levels Firemap uses for Localpayment, the same scale most status pages use. Operational means everything works normally. Degraded means the services work, but some are slower or return more errors than usual. Partial outage means some services, regions or payment methods are unavailable, while the rest still work. Major outage means a key service is unavailable for most customers. When Localpayment publishes it, each official incident also shows its stage: Investigating, Identified, Monitoring or Resolved. In the status history, each day shows its incidents by level, and a purple strip marks days with community reports.
Not on its own. Firemap shows what Localpayment publishes about its platform, not the state of your account. An incident may affect only some regions, payment methods or integrations. Check your own transaction logs and decline codes, and contact Localpayment support with specific transaction IDs if you see failures.
From the official Localpayment status page, once Firemap has connected it. Firemap then reads the page automatically every few minutes and records each status change and incident Localpayment publishes there. Community reports come from PayAtlas users and appear in their own block; they do not change the official status.
They come from different sources. Official incidents are what Localpayment has confirmed, and providers often post one only after the first failures. Community reports come from users and can show a problem earlier, but it may be local: one bank, one country or one integration. Treat reports without an official incident as an early signal, not a confirmed outage.
Start with your own data: error rates, decline codes and response times by payment method, card scheme and country. Compare them with the scope of the incident on the status page. Make sure the backup provider supports the same methods and currencies, move a small share of traffic first, and switch back once the incident is resolved and your metrics recover.
It shows how old the data is instead of guessing. When Firemap has a status for Localpayment, the top of this page shows when Firemap last read the official status page, for example “Updated 2h ago”. If a check fails, the page keeps the last status Firemap read, with its time. If there has been no reading for 7 days, or Firemap has no working status page for Localpayment, the page shows “Status page not connected” instead of a status. The status history counts incidents, so a day without incidents stays green even if the page could not be read that day.
Firemap tracks the official status pages of payment providers listed on PayAtlas. It checks each page automatically and stores every incident with its start time and, once resolved, its end time. When Firemap has data for Localpayment, this page shows 30 days of status history, every official incident that is still open and the resolved incidents that started in the last 30 days. Community reports from the last 30 days are shown for every provider.
Firemap can confirm only what Localpayment has published on its status page: the current status, incidents with their start time and, once resolved, end time, and how long the page has been tracked. It cannot confirm the impact on a specific merchant, transaction or region unless Localpayment says so, and it cannot see problems the provider has not reported.
PayAtlas Stack
Manage Your Payment Stack in One Place
Save the providers you work with and get instant access to their status, coverage, insights, comparisons, and recommended alternatives whenever you need them.
- Free monitoring
- 5 minutes setup
