why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 515adbcad434a7f16d19bc0e6dc5c6e29a342f2f657cd1c41e16b496395127ff
- request
- cca4411f93b70300d15a630289b6abcc945083f4a495a206e443167a193d99df
- transaction
- eca9accaf52e224efc8867e2e2a4f102941b9e815c43262ee35e085d49f68ec5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30320
the chainentry 30320
- sealed to the entry before
- 9d478602571bc874e6b72cb0ae89f459d8125307c02afc4e63724d7e2fdaeb37
- this leaf
- cfe0eb6ebc2ff758dcb94fd9dacd4168b78b3a26c7d6a7a613284790f707bf18
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uQxB1e+6ACIuyF7dPNlr2tz7qYv2+/feV8B1p3gI5C6CNYa6ZGDtxZkTtzpftDmU2MciAXy4beQ0sAhbXkh2AA==