Paysafe has confirmed a security-related incident affecting its PagoEfectivo payment services, resulting in a temporary suspension of payment processing and the permanent deactivation of some merchant API credentials. The incident began on October 29, 2026, and prompted an investigation involving external cybersecurity experts. Although PagoEfectivo services were officially restored on November 1, affected merchants must update their API credentials to reconnect their online stores and resume processing transactions.
The incident is particularly important for e-commerce businesses accepting payments in Peru and Ecuador, where PagoEfectivo enables customers to pay for online purchases through banking applications, payment codes and physical payment locations.
According to Paysafe’s official incident report, the company has implemented additional security measures, strengthened monitoring and established a secure process for issuing replacement API credentials to affected merchants.
What Happened to Paysafe and PagoEfectivo?
The first official notification was published on October 29, 2026, at 21:01 UTC, when Paysafe acknowledged an issue affecting PagoEfectivo services.
Later that evening, the operator confirmed that the underlying cause had been identified and that technical teams were working on a solution.
On October 30, Paysafe reported that PagoEfectivo services would remain temporarily unavailable while its teams investigated the incident and completed the necessary recovery activities. The company described the suspension as a precautionary measure intended to ensure that services could be restored safely.
The most significant security update appeared on October 31 at 08:39 UTC. Paysafe confirmed that its technical teams, supported by external cybersecurity experts, had reviewed the affected environment, addressed the identified issue and strengthened logging and monitoring capabilities.
At the same time, the company announced that some existing merchant API credentials had been permanently disabled.
These credentials can no longer be used to process transactions, meaning affected merchants must receive and configure replacement credentials before their integrations can operate normally.
Paysafe Incident Timeline: October 29 – November 1, 2026
The official incident report provides the following sequence of events:
- October 29, 21:01 UTC: Paysafe identifies a problem affecting PagoEfectivo services.
- October 29, 22:35 UTC: The operator reports that the root cause has been identified and remediation is underway.
- October 30: PagoEfectivo remains temporarily unavailable while technical teams perform security checks, remediation and recovery activities.
- October 31, 08:39 UTC: Services begin returning online. Paysafe confirms the involvement of external cybersecurity experts and the permanent deactivation of some merchant API credentials.
- October 31, 18:26 UTC: A QR code payment partner experiences service degradation. Paysafe redirects traffic through an alternative solution while keeping PagoEfectivo services operational.
- November 1, 05:34 UTC: Paysafe confirms that services remain operational under continued monitoring.
- November 1, 10:31 UTC: Paysafe officially marks the incident as resolved and confirms that PagoEfectivo services have been restored. Merchants requiring replacement credentials are instructed to nominate a technical contact.
The incident is tracked under reference INC0327837.
Although the service disruption has been resolved, individual merchants may still need to update their integrations before payment processing can resume.
Why Has Paysafe Permanently Disabled Some API Credentials?
API credentials authenticate requests between an e-commerce platform and a payment service provider. They allow an integration to identify itself and communicate with payment processing systems.
When an online store uses PagoEfectivo through the Paysafe Payments API, valid credentials are required for the relevant authenticated API operations.
Following the incident, Paysafe permanently deactivated some existing credentials as a protective measure.
The company has confirmed that these credentials are no longer valid for processing transactions. Affected merchants will receive new credentials through a secure procedure involving their designated technical contacts.
Importantly, Paysafe has not publicly established that the credentials were stolen or disclosed to unauthorized parties.
The decision to disable them is a confirmed security measure, but it should not be interpreted as proof that attackers obtained access to merchant API keys.
Similarly, the company has not published technical details demonstrating that customer payment information, card numbers or other personal data were compromised.
What Does the Incident Mean for E-commerce Stores?
For an online retailer, the practical consequences depend on whether its PagoEfectivo integration uses credentials that have been permanently disabled.
An unaffected merchant may be able to continue processing payments without making any configuration changes.
However, a merchant whose credentials have been revoked may experience authentication failures or unsuccessful API requests until replacement credentials are installed.
Potential operational consequences include:
- Failed payment initiation: the store may be unable to create new payment requests using invalid API credentials.
- Checkout interruptions: customers choosing PagoEfectivo may be unable to complete the expected payment process.
- Unpaid or pending orders: orders created during the disruption may require additional verification before fulfillment.
- Payment status inconsistencies: a store may need to reconcile its internal order records with the actual transaction status held by the payment provider.
- Integration downtime: custom payment modules or external applications may need to be reconfigured with replacement credentials.
These are potential consequences of the service interruption and credential deactivation. Paysafe has not confirmed that every affected merchant experienced all of these problems.
How PagoEfectivo Payments Work and Why Transaction Reconciliation Matters
PagoEfectivo is an alternative payment method supported by the Paysafe Payments API, primarily serving customers in Peru and Ecuador.
Unlike conventional card payments, PagoEfectivo allows customers to complete purchases through bank transfers, mobile banking or payments at participating physical locations.
Customers can receive a payment code known as a CIP, which can be used to complete the transaction through supported payment channels.
According to Paysafe’s technical documentation, a typical payment process involves creating a payment handle, redirecting the customer to generate a payment code and waiting for the transaction to be completed.
The payment may initially remain in a processing state until the customer pays. Once payment is completed, the merchant can receive a confirmation through a configured webhook.
This makes accurate reconciliation particularly important following a disruption.
A merchant should not assume that an order has been paid simply because the customer successfully generated a payment code before the incident.
Likewise, a delayed payment confirmation does not necessarily mean that the customer failed to complete the payment.
Store administrators should verify the actual transaction status before changing orders to paid or dispatching goods.
The payment workflow is described in the official Paysafe PagoEfectivo API documentation.
What Should Merchants Do Following the Paysafe Incident?
Businesses using PagoEfectivo should verify their integration even though Paysafe has officially restored the affected services.
1. Confirm Whether Your API Credentials Have Been Deactivated
Check official communications from Paysafe and contact your existing account manager if necessary.
The operator has stated that it will contact merchants whose credentials have been disabled.
Merchants should use established support channels to confirm whether their credentials are affected. Requests involving sensitive API information should be handled only through verified, secure communication channels.
2. Nominate a Technical Contact for Credential Replacement
In its November 1 resolution notice, Paysafe specifically instructed merchants who had not yet done so to nominate a technical contact.
This allows the operator to coordinate the replacement of API credentials through a secure process.
The designated person should have sufficient technical knowledge to update the relevant payment integration or coordinate the change with the company’s website administrator or development team.
3. Update the Payment Integration
Once replacement credentials have been issued, they should be installed in every application that relies on the affected credentials.
Depending on the merchant’s infrastructure, this may include:
- The e-commerce platform’s payment gateway configuration.
- A custom integration communicating directly with the Paysafe Payments API.
- Middleware connecting the storefront to external payment services.
- Additional sales channels or applications using the same merchant integration.
Credentials should be stored in appropriate secret-management or protected configuration systems rather than exposed in public source code, client-side scripts or accessible website files.
After updating the integration, verify that the application can authenticate successfully and communicate with the payment provider.
4. Review Transactions Created During the Disruption
Compare orders recorded by the store against transaction information available from the payment provider.
Pay particular attention to payments initiated between October 29 and October 31, when PagoEfectivo services experienced significant disruption.
Check for:
- Orders that remained unpaid despite customers reporting successful payments.
- Payment requests that failed during initiation.
- Transactions awaiting confirmation.
- Duplicate payment attempts associated with the same order.
- Orders incorrectly marked as completed or cancelled.
Where payment status cannot be established reliably, confirm the transaction through the payment provider before taking action that could affect the customer.
5. Test the Complete Checkout Process
After restoring the integration, perform controlled tests of the payment workflow.
Verify that customers can select PagoEfectivo, create the relevant payment request, receive the necessary payment instructions and return to the store without unexpected errors.
Where supported by the integration, also check that payment status notifications are received and processed correctly.
A successful API authentication test alone does not guarantee that the entire checkout process works as expected.
Could the Incident Affect Payment Security Beyond PagoEfectivo?
The official notification identifies PagoEfectivo as the affected service. Paysafe has not published evidence establishing that all of its payment processing products or merchant services were compromised.
It would therefore be inaccurate to describe the incident as a confirmed security breach affecting every Paysafe customer.
The operator has also not disclosed a public technical report identifying the specific system weakness or explaining whether the incident originated from a cyberattack, unauthorized access or another security-related event.
What is confirmed is that some systems were affected, services were temporarily suspended, cybersecurity specialists assisted with remediation and certain API credentials were permanently disabled.
Businesses using other Paysafe products should follow any relevant official notifications, but they should not assume their integrations require credential replacement solely because PagoEfectivo was affected.
Why Payment API Security Is Essential for Online Stores
Payment processing integrations connect an online retailer’s checkout to external financial infrastructure.
Even when an e-commerce platform itself remains secure and operational, a disruption affecting its payment provider can prevent customers from completing purchases.
For a business running a sklep internetowy (online store), payment availability depends on more than the correct operation of the website.
Valid API credentials, reliable payment notifications, transaction reconciliation and functioning external services are all essential parts of the checkout process.
Companies operating multiple sklepy internetowe (online stores) may face additional complexity when several storefronts or integrations depend on a shared payment provider.
Where several systems use the same credentials, an unplanned credential change may require coordinated updates across multiple applications.
Merchants can reduce operational risk by maintaining accurate documentation of their payment integrations, assigning clear responsibility for API credential management and monitoring payment failures.
It is also advisable to establish a procedure for replacing credentials without exposing sensitive information or unnecessarily interrupting other payment methods.
Paysafe Confirms PagoEfectivo Services Have Been Restored
On November 1, 2026, at 10:31 UTC, Paysafe officially marked incident INC0327837 as resolved.
The operator confirmed that PagoEfectivo services had been restored and that normal operations were resuming as merchants reconnected to its systems.
However, the resolution notice also emphasized that merchants requiring new API credentials should nominate a technical contact so the replacement process could be completed securely.
This means the operator-level incident has been resolved, but individual merchants may still need to take action to restore their own payment integrations.
No public evidence has been provided confirming the theft of merchant credentials or customer payment data. The permanent deactivation of some API credentials remains the most significant confirmed security-related action disclosed by Paysafe.
Online retailers using PagoEfectivo should prioritize verifying their credentials, testing transaction processing and reconciling payments affected by the disruption.
The complete incident history and latest official resolution notice are available on the Paysafe status page for incident INC0327837.