Seven payment and cryptocurrency infrastructure providers reported operational disruptions or technical vulnerabilities on November 3, 2026. Today’s roundup covers multiple Worldpay authorization and acquiring incidents, recurring Colombian payment failures at PayRetailers, a Brazilian Pix Automático disruption at dLocal, delayed merchant confirmations at Xendit, and a temporary Bitcoin transfer problem at Coinbase. PawaPay also experienced another African mobile-money interruption, while a newly filed GitHub report identified unresolved USDT payment-attribution weaknesses in Paykit’s pre-release software.
The incidents involve different payment functions and stages of processing. Several have been resolved, but PayRetailers, Xendit and dLocal continued reporting problems in their latest reviewed notices. None of the providers disclosed transaction volumes or confirmed financial losses attributable to these specific incidents.
Worldpay reports multiple authorization and acquiring failures
Worldpay recorded four service-resolution notices on November 3, including a third-party 3D Secure authentication failure that occurred between 09:30 and 10:15 UTC.
Under incident INC0716051, the processor confirmed that its third-party provider had resolved the technical issue, formally announcing recovery at 10:55 UTC. The disruption lasted approximately 45 minutes, although Worldpay did not quantify how many payment authentications failed or were delayed.
3D Secure is used to authenticate customers during certain card transactions. Failures in this process can interrupt purchases before authorization is completed, but Worldpay’s notice does not establish whether transactions were declined, abandoned or successfully retried during the incident.
A seperate Acquiring Services incident, INC0716043, was declared resolved at 10:29 UTC. Worldpay provided no detailed technical explanation or affected-transaction figures.
Earlier that morning, the company closed two additional notices under reference INC0714904. Integrated Payments authorization and payment services were restored at 05:46 UTC, followed by Sterling File Gateway acquiring services at 06:07 UTC.
Four notices in one morning, but no confirmed shared technical cause.
The sequence follows Worldpay’s October 29 payment-processing disruption, when an internal database issue following scheduled maintenance affected card payouts, refunds and order-management functions.
The November 3 incidents covered different services and included an explicitly identified third-party authentication failure. Worldpay has not established a connection with the earlier database problem.
PayRetailers and dLocal face payment-rail problems in Latin America
PayRetailers reported two Colombian payment-service incidents on November 3, affecting Bre-B instant payments and conventional bank-transfer payouts.
The first began at 01:45 UTC, when PayRetailers detected declining approval rates for Bre-B pay-ins and payouts. The company implemented a fix at 01:54 UTC and declared the incident resolved at 02:26 UTC, approximately 41 minutes after its initial notification.
A second incident emerged at 06:31 UTC, involving decreased approval rates for Colombian bank-transfer payouts. The company said it was monitoring external payment networks and investigating the problem. No resolution was available in the latest reviewed notice.
Two disruptions in the same country, just hours apart, and still no established connection.
The incidents follow another Bre-B pay-in approval problem recorded between October 30 and 31. The repeated reports identify difficulties involving Colombian payment integrations, but the published evidence does not show whether a single banking partner, clearing component or technical defect caused the interruptions.
Bre-B operates within Colombia’s regulated interoperable instant-payment framework. The latest PayRetailers notices do not indicate a nationwide failure of the system.
Brazilian payment processor dLocal separately acknowledged processing difficulties involving Dlocal Bank–Pix Automático at 08:24 Brasília time, equivalent to 11:24 UTC.
The company said it had contacted the processor and was investigating the incident. Its initial disclosure did not establish whether affected payments were rejected, delayed or awaiting confirmation.
Pix Automático supports automated recurring payments under the Central Bank of Brazil’s framework, allowing customers to authorize periodic collections such as subscriptions, insurance premiums and utility bills.
For merchants using the affected dLocal integration, the unresolved technical question concerns the execution status of scheduled debits. A retry after an uncertain payment result requires accurate confirmation of whether the initial collection was completed. No duplicate charges or failed subscription collections have been confirmed from this incident.
The disruption is specific to the processor integration identified by dLocal, rather than evidence of a broader Brazilian Pix outage.
Xendit, Coinbase and PawaPay report transaction delays
Xendit disclosed another payment-notification problem in Indonesia, this time affecting a small percentage of Bank Rakyat Indonesia (BRI) Virtual Account transactions.
According to its November 3 incident notice, the disruption began at 04:00 Western Indonesian Time. Xendit attributed the delays to a banking-partner issue and said customer payments were continuing to process normally.
Merchants, however, could recieve transaction-status updates and payment callbacks later than expected.
The customer has paid, but the merchant may still be looking at an unpaid order.
The issue resembles Xendit’s earlier payment and payout disruptions across three Asian markets, including delayed QR payment notifications in the Philippines during October 28–29.
In those earlier incidents, some completed transactions remained without timely merchant confirmation, prompting reconciliation procedures and warnings against requesting duplicate payments.
The November 3 BRI notice did not disclose a transaction backlog, confirmation-delay duration or resolution time. Xendit said it was working with its banking partner to restore normal notification delivery.
Coinbase experienced a different problem involving delayed Bitcoin transfers during the early hours of November 3 UTC.
The cryptocurrency exchange began investigating delayed BTC sends at 01:20 UTC and declared the incident resolved at 02:27 UTC, giving the disruption a reported duration of approximately 67 minutes.
Coinbase explicitly stated that Bitcoin receives, cryptocurrency buying and selling, and fiat deposits and withdrawals were unaffected. The exchange also assured customers that their funds remained safe.
The company implemented a fix before closing the incident but did not disclose the underlying technical cause, number of delayed transactions or whether the interruption involved transaction broadcasting, internal withdrawal processing or another component.
The disruption was limited, atleast in the company’s published description, to outgoing Bitcoin transfers.
Separately, PawaPay reported instability affecting both deposits and payouts through Lesotho’s M-Pesa mobile-money services.
The incident began at 00:56 UTC, with PawaPay escalating the issue to the mobile-money operator. At 01:51 UTC, the company reported improving transaction success rates before declaring the incident resolved at 02:21 UTC.
Both collection and disbursement channels were affected this time, rather than only one side of the payment process.
PawaPay has experienced several recent mobile-money disruptions across African markets, including earlier outages involving operators in five African countries during October 27–28.
The Lesotho episode lasted approximately 85 minutes between the initial notice and formal recovery. PawaPay disclosed neither affected transaction counts nor financial losses, and it has not connected the incident to its earlier regional service problems.
Paykit bug report identifies unresolved USDT payment-attribution risks
A newly opened technical issue in Paykit’s open-source payment-server repository identifies two weaknesses affecting USDT payment evidence and the handling of completed payment drains.
GitHub issue #123 was opened on November 2 at 22:06 UTC, equivalent to November 3 at 00:06 Cairo time. The report concerns Paykit v0.1.1-rc5 and proposed changes to how payment evidence is attributed to individual payment requests.
The first issue involves payment drains completed before database migration 0023. According to the report, a drain could remain marked completed after reconciliation invalidates the USDT payment evidence that originally supported it.
Existing replay and cleanup restrictions may then prevent the completed state from being corrected, leaving the associated active drain identifier blocking further processing for that lock generation.
The second weakness concerns the time window used to determine whether a USDT transfer belongs to a particular payment request.
Rather than using the proposal time of the individual payment attempt, the implementation can use the earliest recorded proposal time associated with the invoice. This may allow evidence from one attempt to be evaluated against another attempt’s earlier attribution window.
The report identifies a similar concern affecting Marketplace status_usdt processing.
In some cases an earlier payment attempt supplies the timing reference, even when the evidence being checked belongs to a later attempt.
The proposed correction would associate verified USDT observations with their corresponding payment-request attempts and recompute retained drain summaries during migration or a subsequent reconciliation process.
For legacy observations that cannot be reliably attributed to an individual attempt, the report recommends rejecting the evidence until it can be verified again.
The issue also clarifies that version 0.1.0 did not previously enforce the proposal-time restriction, so the identified gaps are not regressions introduced by the related change. Existing implementation work already includes some safeguards against accepting evidence when the proposal time is unknown.
This remains a code-level finding in pre-release software. The report provides no evidence of a production exploit, unauthorized USDT withdrawals or customer financial losses.
The technical gap is documented, but a succesful attack has not been demonstrated.
Across the November 3 developments, the outstanding operational questions differ considerably. Worldpay, Coinbase and PawaPay have issued recovery notices, while PayRetailers, Xendit and dLocal still have unresolved payment-service reports in their latest disclosures. Paykit’s issue remains an implementation problem requiring further development and testing, with no demonstrated incident involving customer funds.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape. You can reach out to him via his social media accounts:
Linkedin: https://www.linkedin.com/in/johan-shamshad-742851262/
X: https://x.com/Yasmine_FX
Investing: https://www.investing.com/members/contributors/279781574