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
- ccd90090286f57d205f814b5724d88ff8e81830d9a3b04a7f886b070c24ff001
- request
- 73dd606e59cbbb2bf32d98a2f9255d232d0618e24b8440430ab47ff9dcc4a67a
- transaction
- 58a184d418405082d1bcfb60b8324d5896bc7047ba8e683d44621fd46719a7ffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63235
the chainentry 63235
- sealed to the entry before
- ce1a62994e867aeb875ce803c4eb174a7215fcdb467a66b59dca1dc044bf21c8
- this leaf
- e7bfdde7b092087edfa22cca3696a31444434ec9053242fe430868334326a69d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vAR54x3e5qsRD8qb0X3PNzMi9N1oSmvGmSIsfgH1KpRJgAJhIXXsfADPO54JcgUkb7LbSl0DYwf0XvuXAzJOCg==