Is DNA Payments down?
DNA Payments 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
- 0
- Major outage
- 0
- Community signals
- 0
-
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 1
- 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
- 1
- 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
- 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
- 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 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
- 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
-
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
- 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
-
Oct 26
- 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
-
Nov 2
- Degraded
- 0
- Partial outage
- 0
- Major outage
- 0
- Community signals
- 0
-
Nov 3
- 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
- 2
- 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 DNA Payments down for you?
-
Degraded∙ Duration 15m
Affected: DNA
We are currently investigating this issue.
This incident has been resolved.Degraded → Resolved 2d ago
Resolved
-
Degraded∙ Duration 17m
Affected: DNA
We are currently investigating this issue.
Investigations showed that a network route was becoming intermittently unavailable and has been taken out of service. Authorisation traffic is now processing normally.Degraded → Resolved 1w ago
Resolved
-
Degraded∙ Duration 14m
Affected: LIVE - Authorisations DNA
We are aware of potential issues with authorisations and are actively investigating.
Authorisation issues have been resolvedDegraded → Resolved 1w ago
Resolved
-
Partial outage∙ Duration 43m
Affected: Global Payments
We are aware of potential issues with authorisations and are actively investigating.
This incident has been resolved.Partial outage → Resolved 2w ago
Resolved
Services
No currently affected DNA Payments services
There are no reported issues with this provider’s services in the last 24 hours.
-
LIVE - Authorisations
Authorisation status
Operational -
LIVE - Submissions
Status of settlement submissions to acquirers
Operational -
LIVE - OCC
Production OCC Status
Operational -
LIVE - Core Infrastructure
The core infrastructure, including datacentres and networks.
Operational -
LIVE - Terminals
Operational -
PreProduction and Test
Operational -
AIBMS
Status of AIBMS acquiring
Operational -
American Express
Status of Amex acquiring
Operational -
Barclaycard
Status of Barclaycard acquiring
Operational -
Clearhaus
Status of Clearhaus acquiring
Operational -
DNA
Acquiring status for DNA Payments
Operational -
Elavon
Status of Elavon acquiring
Operational -
FDMS
Status of FDMS acquiring
Operational -
FIS (WorldPay)
Status of FIS (WorldPay) acquiring
Operational -
Lloyds Cardnet
Status of Lloyds Cardnet acquiring
Operational -
Park Card Services/Flexecash
Status of Park Card Services/Flexecash acquiring
Operational -
UnionPay
Operational -
Global Payments
Operational -
PayCore
Operational -
Valitor
Operational -
3D Secure Services
External 3D Secure Services
Operational -
Mobile Data Provider
Operational
About DNA Payments status page
- Monitoring since Oct 2026
- 22 services and components tracked
- 58 incidents total
- Last updated: Nov 17, 2026
Saw an error in description or reports for DNA Payments?
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. DNA Payments reports normal operation on its official status page. Firemap last read the status page today at 14:18 UTC.
They are the four status levels Firemap uses for DNA Payments, 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 DNA Payments 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 DNA Payments 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 DNA Payments, 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 DNA Payments services that work normally right now. Incidents, Community reports and Uptime are compared with the previous 30 days. If Firemap has not tracked DNA Payments 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 DNA Payments 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 DNA Payments 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 DNA Payments support with specific transaction IDs if you see failures.
From the official DNA Payments 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 DNA Payments 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 DNA Payments 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 DNA Payments.
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 DNA Payments, 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 DNA Payments, 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 DNA Payments, 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 DNA Payments 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 DNA Payments 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.