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
- 1535a1ea3093ab3fe4230a4f4d9c5d14c51b476e000cd93de2c4ee7357b9b2e2
- request
- 21a3d91d6e1343a0ea16e5ce73ac59b9779ab463c8a60b2432dddac1ddd51bb0
- transaction
- 03b7b9794031eaeec421777adb1cee95efc73fa40f864bab601b06cad9b0716fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67245
the chainentry 67245
- sealed to the entry before
- cce9d258da9e50cae9551be760e40d50fd495bdd3d3590931088c1e7299f15fd
- this leaf
- ce14f983455af1aa05c8f3d4542faf870a7a388a3e6b5ce015b2018306d377e4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2UQEwF6awO8J7vpaoBWm8TjnoC8d57BlalPFCwaoBt1CWVaoDWAOBMkwoplxXRI71AQmF6Fx0kUTQfvR1WJfCQ==