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
- 885f49635ff2a0c349fa506c0fa10ce763b80b0bea5cb5fadeb26f307810b128
- request
- 8008cf0284266c2c839ee5c44311746cfcffc799ecb984cb29ee0f64d030d222
- transaction
- 8d7dd019b7eb3a2bdc642c754cd0c507da27ef9a43b0f612cc9c4a4908bf9ac7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58587
the chainentry 58587
- sealed to the entry before
- 1976a9f0c5e21455e07c08a8c24272e0df210dd1460f8056f312b4cb56462694
- this leaf
- eae4e40db54b980b57a7b4a5fe51a312922ef1f2acb72c2324941fd23e2564d9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cJK10sLgEXsZg2cqjchokwNtJTz/a8MnhW4g4MuJskDktsnIwLx1iuX8w6T90yrmQ6OnwuGwaRcfU4BmxZDsAA==