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
- 3bdd4b50f873307b5926ad2542b52c7be2fe58140866bc961dbeb33306cd241f
- request
- e0cc4ef22eff529919e0693bdd3bf66c6ea5ce9f152cafc49679cf2235ad5f68
- transaction
- 22eb2a80ca155d891c746821bfacb16195542e28e62fbb1c75b6bd6e3b646a67computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 506
the chainentry 506
- sealed to the entry before
- 9c6f0c3cbdf375efe829b80d2d90b2d122850e3fabf47407ea0329d5fcf9b344
- this leaf
- fa39c69efeeeab19ea299e9143f577d682fd3db688140750a6f25c066cea9fab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- J3jGGW7Ea1c2vkmv4aYDJHKcv39X7AWDhTyM9o3iNEBIU048fmuGMPrtk+emeyqtmtjDtWP8oBDLlsWiRUwjAg==