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
- f9f4dd49faa08502f9eb2d6bfbd1fed507baa9d844663b279bec539576f7e672
- request
- 58384915d9499d239509bd5fa86ceb03ffa98c74280cfd73beedbadadea937c5
- transaction
- fd7cc1ad4d0b43c18de2f446a6aabc33b1fed7c835448bc3c6d693d88eb244efcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1860
the chainentry 1860
- sealed to the entry before
- 77811fa7a3a2b526927caa12b600afddd7c441b7a8d1470c436e02800e4e4510
- this leaf
- 21c8e1489ff0bed7f75048130a9b74665baa623acae87054a1dfdd7f4fecd872
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jWTd8jRnjda1YUXF2F3XWL2xM0JPYk8Mz3ggHUWBO1mJ7y5pNgGwU1PeyQiR1TNHS9RyGMbMW+evnZDlEwaxAg==