Is Treezor down?
Treezor is operational.
There are no reported issues with this provider’s services in the last 24 hours.
Updated just now
Reliability snapshot
Last 30 days
Incidents timeline
2 peak
2 peak
2 peak
- Operational
- Degraded
- Partial outage
- Major outage
- Community report
-
Aug 20
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 1
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Sep 11
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Sep 19
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 1
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Oct 4
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 2
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Oct 19
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 1
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Oct 26
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 1
- Partial outage
- 1
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Nov 2
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Nov 3
- Degraded
- 1
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Nov 10
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 1
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Nov 17
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
Community reports
No community reports yet
No community members have reported issues with this provider.
Is Treezor down for you?
-
Degraded∙ Duration 17m
Affected: CARD - Authorization Processing Service (Production)
Dear customers,
Our card processing partner has informed us of an ongoing incident currently affecting card authorization services. At this stage, some authorizations are being impacted intermittently.
Our partner is actively working to resolve the issue as quickly as possible, and we will share further updates as soon as they become available.
We apologize for any inconvenience caused and thank you for your understanding.
Best regards.
Treezor team
Dear customers,
Our card processing partner has informed us that the issue has been resolved.
Authorizations processing is now fully operational.
Best regards,
This incident has been resolved.Degraded → Resolved 2d ago
Resolved
-
Degraded∙ Duration 1h
Affected: SCA - Mobile App
Dear customers,
Our SCA partner is facing an incident impacting authentication.
Users may experience errors during SCA wallet activation and lock/unlock.
Our partner is working to resolve the issue as quickly as possible.
We apologize for any inconvenience this may cause and thank you for your understanding.
Best regards.
Treezor team
We are continuing to monitor for any further issues.
This incident has been resolved.Degraded → Resolved 2w ago
Resolved
-
Partial outage∙ Duration 2h
Affected: CARD - Tokenization Service (Production)
Dear customers,
We are currently experiencing delays and delivery failures for SMS one-time passwords (OTP) due to an upstream issue with our provider (OVH). As a result, users may experience difficulties receiving verification codes to log in or authorize operations.
Our engineering team is closely monitoring the situation alongside the provider to restore normal delivery as quickly as possible.
We will provide an update as soon as more information becomes available.
Best regards.
Treezor team
As of 11:36 AM CET, transaction processing has returned to normal.
All services are fully operational.Partial outage → Resolved 3w ago
Resolved
-
Degraded∙ Duration 1m
Dear customers,
Between 10:00 AM and 10:20 AM, we experienced elevated latency and intermittent timeouts affecting some of our services, including agent-facing tools and card operations.
Our engineering team identified the issue and applied a fix. All systems are now operating normally, and we are monitoring performance closely.
We apologize for any inconvenience caused.
Regards,
Treezor teamDegraded → Resolved 3w ago
Resolved
Services
No currently affected Treezor services
There are no reported issues with this provider’s services in the last 24 hours.
-
API (Preproduction)
Treezor Core Banking API Preproduction
Operational -
Webhooks (Preproduction)
Notifications from Treezor Core Banking
Operational -
KYC document (Preproduction)
Operational -
KYC liveness (Preproduction)
Operational -
Card acquiring (Preproduction)
Operational -
Cheque acquiring (Preproduction)
Operational -
SEPA Credit Transfer - Emission (SCTE) (Preproduction)
SCT management services, outgoing transfers.
Operational -
SEPA Credit Transfer - Reception (SCTR) (Preproduction)
SCT management services, incoming transfers.
Operational -
SEPA Instant Credit Transfer - Emission (SCTE Inst) (Preproduction)
SCT management services, outgoing instant transfers.
Operational -
SEPA Instant Credit Transfer - Reception (SCTR Inst) (Preproduction)
SCT management services, incoming instants transfers.
Operational -
SEPA Direct Debit - Reception (SDDR) - B2B (Preproduction)
Operational -
SEPA Direct Debit - Reception (SDDR) - Core (Preproduction)
Operational -
SEPA Direct Debit - Emission (SDDE) - Core (Preproduction)
Operational -
CARD - Lifecycle (Preproduction)
This service processes the creation and update from our card partner.
Operational -
CARD - Authorization Processing Service (Preproduction)
This service processes the authorizations received from our card partner.
Operational -
CARD - Settlement Processing Service (Preproduction)
This service processes settlements received from our card partner.
Operational -
CARD - Tokenization Service (Preproduction)
Operational -
Dashboard Connect (Preproduction)
Operational -
SCA - Mobile App
This component concerns SDK services of our provider
Operational -
API (Production)
Treezor Core Banking API PRODUCTION
Operational -
Webhooks (Production)
Notifications from Treezor Core Banking
Operational -
KYC document (Production)
Operational -
KYC liveness (Production)
Operational -
Card acquiring (Production)
Operational -
Cheque acquiring (Production)
Operational -
SEPA Credit Transfer - Emission (SCTE) (Production)
SCT management services, outgoing transfers.
Operational -
SEPA Credit Transfer - Reception (SCTR) (Production)
SCT management services, incoming transfers.
Operational -
SEPA Instant Credit Transfer - Emission (SCTE Inst) (Production)
SCT management services, outgoing instant transfers.
Operational -
SEPA Instant Credit Transfer - Reception (SCTR Inst) (Production)
SCT management services, incoming instants transfers.
Operational -
SEPA Direct Debit - Reception (SDDR) - B2B (Production)
Operational -
SEPA Direct Debit - Reception (SDDR) - Core (Production)
Operational -
SEPA Direct Debit - Emission (SDDE) - Core (Production)
Operational -
SEPA Direct Debit - Emission (SDDE) - B2B (Production)
Operational -
CARD - Lifecycle (Production)
This service processes the creation and update from our card partner.
Operational -
CARD - Authorization Processing Service (Production)
This service processes the authorizations received from our card partner.
Operational -
CARD - Settlement Processing Service (Production)
This service processes settlements received from our card partner.
Operational -
CARD - Tokenization Service (Production)
Operational -
Dashboard Connect (Production)
Operational -
Treezor Documentation
https://docs.treezor.com/
Operational -
KYC Services Disruption
This component concerns KYC services that are not linked to our APIs.
Operational -
Other Disruption
This component concerns services that are not linked to our APIs, including our providers.
Operational -
SCA - Mobile App
This component concerns SDK services of our provider
Operational -
SEPA Disruption
This component concerns the SEPA service, which is not linked to our APIs.
Operational
About Treezor status page
- Monitoring since Oct 2026
- 43 services and components tracked
- 59 incidents total
- Last updated: Nov 17, 2026
Saw an error in description or reports for Treezor?
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. Treezor reports normal operation on its official status page. Firemap last read the status page today at 14:06 UTC.
They are the four status levels Firemap uses for Treezor, 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. The same levels color the status banner, the official incidents and the services. When Treezor publishes it, each official incident also shows its stage: Investigating, Identified, Monitoring or Resolved. In the Incidents timeline, each day shows its incidents by level, and a purple strip marks days with community reports.
Uptime is the share of time in the last 30 days when Treezor reported normal operation on its status page. Degraded performance and outages count as downtime. Time when Firemap could not read the page counts as normal, because there is no evidence of a problem. The value is rounded down to two decimals. When Firemap has data for Treezor, the Reliability snapshot shows Uptime next to three more numbers: Incidents, the official incidents that started in the last 30 days; Community reports from the same days; and Service availability, the share of Treezor services that work normally right now. Incidents, Community reports and Uptime are compared with the previous 30 days. If Firemap has not tracked Treezor for that long, Incidents and Uptime show “No data for previous 30 days”.
Select an incident in the Official incidents block. A panel opens with the incident level, the affected services when the status page lists them, the start and, once resolved, the end time, and the updates Treezor posted, newest first. Each update shows when it was posted and its stage: Investigating, Identified, Monitoring or Resolved. Some status pages publish updates without stages, or no separate updates at all; the panel then shows the updates without a stage, or says that there are none.
Not on its own. Firemap shows what Treezor 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 Treezor support with specific transaction IDs if you see failures.
From the official Treezor status page, once Firemap has connected it. Firemap then reads the page automatically every few minutes and records each status change, incident and incident update Treezor 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 Treezor 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.
Use Report issue on this page or, when there are no reports yet, one of the problem buttons in the Community reports block. Sign in, choose what you see: Completely down, Partial outage, Very slow or Showing errors, and describe the problem: what fails, where and since when. Your report appears in the Community reports block at once. Reports do not change the official status of Treezor.
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 Treezor, 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 Treezor, the page shows “Status page not connected” instead of a status. The Incidents timeline 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 Treezor, this page shows an Incidents timeline of up to 90 days, 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 Treezor has published on its status page: the current status, incidents with their start time and, once resolved, end time, the services and updates the status page lists for each incident, and how long the page has been tracked. It cannot confirm the impact on a specific merchant, transaction or region unless Treezor says so, and it cannot see problems the provider has not reported.
PayAtlas Firemap
Monitor the health of 200+ payment providers, track active incidents, and spot ecosystem-wide disruptions in real time.
Stay on top of your payment stack
Add your payment providers to Stack and get updates on incidents, outages and service status changes in one place.
- Monitor the providers you rely on
- Get notified about status changes
- Spot issues before they affect your payments
Incident Updates Timeline
Couldn’t load the incident.