Three developments on November 4, 2026, exposed different problems in cryptocurrency payment infrastructure. Paxos experienced a three-hour transfer API outage followed by extended deposit-processing delays, Kraken restored Brazilian real deposits while PIX withdrawals remained disrupted, and Bitget published new guidance on additional compliance checks required by some fiat-payment providers. The latest crypto payments roundup covers the recovery timelines, the remaining restrictions and the role of external service providers in processing customer transactions.
Paxos restores crypto transfers after three-hour API outage
Paxos experienced a cryptocurrency transfer outage on November 4 that disrupted deposits and withdrawals through its dashboard and v2 application programming interface (API). The company first reported the problem at 15:04 UTC, identifying an outage affecting its Transfers endpoints.
At 15:43 UTC, Paxos announced that its engineering team had identified the root cause and was preparing a fix for pending withdrawals. The company said those withdrawals would be processed once the correction was deployed.
Further updates at 16:30 and 17:34 UTC confirmed that some withdrawals could remain pending while engineers continued working. Paxos marked the transfer incident resolved at 18:15 UTC, approximately three hours and 11 minutes after the initial notification.
But deposits were still not fully back to normal.
A separately tracked incident affecting cryptocurrency deposits remained active after the main transfer outage had been resolved. Paxos reported at 19:15 UTC that some deposits were experiencing delayed processing, with engineering teams continuing to work on a correction.
At 20:13 and 21:09 UTC, the company said it was reviewing a potential fix. The deposit incident was finally marked resolved at 22:01 UTC, when Paxos confirmed that all deposits were operational and previously delayed transactions had been processed.
The second incident therefore remained open for six hours and 57 minutes from its recorded 15:04 UTC start, extending three hours and 46 minutes beyond the resolution of the main transfer outage.
The deposits took longer to clear, even after the wider transfer service was back.
Both incident records identify the same dashboard and API components, but Paxos has not published a detailed explanation establishing whether they resulted from a single technical failure. The company also did not disclose affected transaction volumes, the value of pending transfers or which institutional customers experienced delays.
The incident adds to recent concerns about the reliability of crypto payment infrastructure, where transaction verification, execution and final settlement can depend on seperate processing components.
Kraken’s Brazilian PIX withdrawals remain delayed
Kraken continued investigating delays affecting Brazilian real withdrawals through the PIX payment network on November 4, even after restoring normal deposit processing.
The exchange initially reported the disruption at 20:39 UTC on November 3, warning that both deposits and withdrawals could remain pending longer than usual.
At 13:39 UTC the following day, Kraken confirmed that BRL deposits through PIX were operating normally again. Withdrawals, though, were still taking longer, and the exchange continued working with its payment provider.
That left customers with a rather uneven recovery: deposits were functioning, while some outgoing payments remained delayed.
The incident had remained active for more than 25 hours by late November 4. Kraken’s published status record did not identify the payment provider, disclose the outstanding withdrawal amount or provide a timetable for full recovery.
PIX is Brazil’s instant-payment system, developed by Banco Central do Brasil. According to the central bank’s official explanation of PIX, the network normally enables transfers within seconds, operates continuously and supports payments between participating financial institutions.
Kraken’s incident concerns its BRL funding integration rather than a confirmed nationwide disruption of the PIX network. The exchange attributed its recovery efforts to coordination with its provider but did not specify where the procesing problem originated.
The disruption follows a September 4 incident involving Kraken’s euro withdrawals through Banking Circle. In that case, the exchange explicitly identified its banking provider as the source of the delays, with the incident lasting approximately five hours and 46 minutes.
More recently, Kraken experienced multiple funding and trading-service disruptions, including prolonged US futures maintenance and cryptocurrency funding delays in late October.
Those previous incidents involved different systems and providers, and the available evidence does not establish a shared technical cause.
For the Brazilian PIX incident, the unresolved details include whether delayed withdrawals had already been submitted to the payment provider, whether transactions required resubmission and how many customers were affected.
Bitget details additional fiat-compliance requirements
Bitget published a support notice on November 4 explaining an additional verification procedure that some customers must complete before continuing to use fiat deposit and cryptocurrency purchase services.
The guidance, published at 14:09 according to the exchange’s website, describes a Fiat Questionnaire required by certain third-party financial service providers.
Bitget explained that its fiat services depend on external partners whose regulatory and compliance obligations can require additonal customer information beyond the exchange’s existing account-verification procedures.
Affected customers encounter a notification when accessing Bank Deposit or Buy/Sell Crypto services. They must complete and submit the questionnaire before they can continue using the services subject to that requirement.
Completing the form is one stage; getting the provider’s approval is another.
Submissions can carry three principal statuses: pending submission, under review, or rejected with further information required. Customers whose responses are rejected may need to correct their information and submit the questionnaire again.
Bitget said review times vary according to the questionnaire and the specific fiat-service provider. An estimated timeframe is displayed after submission, rather than a single platform-wide deadline.
The explanation leaves several questions unanswered. Bitget has not publicly identified which partners require the questionnaire, the countries affected or the number of customers subject to further review.
The November 4 publication documents the compliance procedure but does not establish that Bitget introduced a new universal verification requirement that day. Nor does it quantify how frequently customers are prevented from completing bank deposits or crypto purchases while awaiting approval.
There is another review layer here, and its timing depends on the payment partner.
Across the three developments, the operational outcomes differ. Paxos confirmed complete recovery of its delayed cryptocurrency deposits by 22:01 UTC on November 4. Kraken had restored PIX deposits but had not announced a resolution for affected BRL withdrawals in its latest published incident update. Bitget’s disclosure describes an ongoing provider-dependent verification process rather than a reported system outage.
For customers and businesses relying on these services, the outstanding gaps are specific: Kraken has yet to disclose the volume and expected clearance time of delayed Brazilian withdrawals, while Bitget has not detailed the geographic or provider-level scope of its questionnaire requirements. Paxos has confirmed the clearance of delayed deposits, although the full transaction impact and the relationship between its two incident records remain undisclosed.
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