SaaS Ranking
Menu

IXOPAY

ixopay.com · Payment orchestration · checked 2026-09-04

50/100DBand D

Rank 1 of 22 in Payment orchestration, where the median is 19.5.

We measured 10 of 12 criteria for IXOPAY on 2026-09-04. We found 4 with a source and did not find 6 at the addresses we checked; 2 we could not measure at all. That is a transparency score of 50 out of 100, band D.

Overview

Transparency labelsaas-ranking.com

IXOPAY

ixopay.com · Payment orchestration

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
D 50of 100 Rank 1 of 22

Published commitments4 of 9 found

Measured behaviour0 of 1 found, 2 not measured

Checked 2026-09-04. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that IXOPAY has no such document.

What they state

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

✗

Data location stated

weight 3 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://www.ixopay.com/legal/privacy-notice · checked 2026-09-04

Show the 7 addresses we checked
  1. https://ixopay.com/security – reached, no match (HTTP 404)
  2. https://ixopay.com/trust – reached, no match (HTTP 404)
  3. https://ixopay.com/legal/privacy – reached, no match (HTTP 404)
  4. https://ixopay.com/privacy – reached, no match (HTTP 404)
  5. https://ixopay.com/privacy-policy – reached, no match (HTTP 404)
  6. https://ixopay.com/compliance – reached, no match (HTTP 404)
  7. https://ixopay.com/legal/privacy-policy – found, but behind a sign-in

Is this wrong? Send us the URL

✗

Public pricing

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-04.

Show the 5 addresses we checked
  1. https://ixopay.com/pricing – reached, no match (HTTP 404)
  2. https://ixopay.com/pricing/ – reached, no match (HTTP 404)
  3. https://ixopay.com/plans – reached, no match (HTTP 404)
  4. https://ixopay.com/en/pricing – reached, no match (HTTP 404)
  5. https://ixopay.com/pricing-plans – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

  • HSTS max-age 31536000 seconds (365 days).
    Show the exact wording

    max-age=31536000; includeSubDomains; preload

    Read at https://ixopay.com/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=31536000; includeSubDomains; preload

    Read at https://ixopay.com/

    max-age=31536000; includeSubDomains; preload

    Read at https://ixopay.com/

Checked 2 addresses on 2026-09-04.

Show the 2 addresses we checked
  1. http://ixopay.com/ – HTTP 301, no redirect to HTTPS
  2. https://ixopay.com/ – HSTS max-age=31536000

Is this wrong? Send us the URL

✗

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-04.

Show the 6 addresses we checked
  1. https://ixopay.com/security – reached, no match (HTTP 404)
  2. https://ixopay.com/trust – reached, no match (HTTP 404)
  3. https://ixopay.com/trust-center – reached, no match (HTTP 404)
  4. https://ixopay.com/compliance – reached, no match (HTTP 404)
  5. https://ixopay.com/legal/security – reached, no match (HTTP 404)
  6. https://trust.ixopay.com/ – The name "trust.ixopay.com" could not be resolved.

Is this wrong? Send us the URL

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-04.

Show the 6 addresses we checked
  1. https://ixopay.com/legal/sla – reached, no match (HTTP 200)
  2. https://ixopay.com/sla – reached, no match (HTTP 404)
  3. https://ixopay.com/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://ixopay.com/trust/sla – reached, no match (HTTP 404)
  5. https://ixopay.com/uptime – reached, no match (HTTP 404)
  6. https://ixopay.com/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Named privacy contact

weight 1 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://www.ixopay.com/legal/privacy-notice · checked 2026-09-04

Show the 7 addresses we checked
  1. https://ixopay.com/legal/privacy – reached, no match (HTTP 404)
  2. https://ixopay.com/privacy – reached, no match (HTTP 404)
  3. https://ixopay.com/privacy-policy – reached, no match (HTTP 404)
  4. https://ixopay.com/legal/privacy-policy – found, but behind a sign-in
  5. https://ixopay.com/legal/privacy-notice – found, but behind a sign-in
  6. https://ixopay.com/trust/privacy – reached, no match (HTTP 404)
  7. https://ixopay.com/datenschutz – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 4
✓

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://www.ixopay.com/legal/dpa · checked 2026-09-04

✓

Subprocessor list

weight 3 of 3

The actual list is published, not just a promise to keep one.

Source: https://www.ixopay.com/legal/subprocessors · checked 2026-09-04

✓

Status page with history

weight 2 of 3

A public status page with incident history.

Source: https://status.ixopay.com/ · checked 2026-09-04

✓

Notice before subprocessors change

weight 2 of 3

The vendor commits publicly to giving notice before the list changes.

Source: https://www.ixopay.com/legal/dpa · checked 2026-09-04

Not measured by us 2
–

No third-party tracking before consent

weight 2 of 3

Not measured. The page could not be loaded in a browser, so this was not measured.

Show the 1 address we checked
  1. https://ixopay.com/ – page.waitForTimeout: Page crashed

Is this wrong? Send us the URL

–

security.txt (RFC 9116)

weight 1 of 3

Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.

Show the 1 address we checked
  1. https://ixopay.com/.well-known/security.txt – blocked or unavailable (HTTP 403)

Is this wrong? Send us the URL

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Compare