security.txt (RFC 9116) in Payment orchestration
It tells a researcher where to report a vulnerability instead of guessing.
0 of 13 vendors we measured here publish it, that is 0%. Last checked 2026-09-03.
0% here against 13% across every category we measure. Payment orchestration sits below the overall share for this criterion.
Back to security.txt (RFC 9116) across all categories, or to Payment orchestration.
Published
Served at /.well-known/security.txt.
None of the vendors we measured here published this.
No security.txt found.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| Akurateco | 1 address checked |
| BR-DGE | 1 address checked |
| Column | 1 address checked |
| Corefy | 1 address checked |
| Enfuce | 1 address checked |
| Gr4vy | 1 address checked |
| Highnote | 1 address checked |
| Marqeta | 1 address checked |
| Primer | 1 address checked |
| ProcessOut | 1 address checked |
| Spreedly | 1 address checked |
| Toqio | 1 address checked |
| Weavr | 1 address checked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
| Vendor | What we found |
|---|---|
| Cellulant | The vendor’s server blocked or rate-limited our crawler, so this was not measured. |
Found something we missed? Tell us and the next run picks it up.