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
- 8499cb594cf43de041e16f5422120573f20f78611f6500e5a09fe01b71878599
- request
- 6dd3c0bac322e2babd1cd713bfb71088dccc9048f688486a1fdf3c0f3f148a19
- transaction
- 513b93f99a9dfc0fbdf03b1fdc5bf71699cd82c17495bde38ea5f7a6c4c5571bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43662
the chainentry 43662
- sealed to the entry before
- 3cdb531874d3800e168d2f788e34bc94abc387293890d38a187d05b8b5cd03ae
- this leaf
- a1eb83f365d7ba3382010f504c99f0ba7e603e847c61c04ad19768ae5bdf96aa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NpmTXiS8UN5PGk5sbKTy55K+mJg5Me+U9kBjxeXgqA27buRhXqMi/5lrWZ6B5oeDHBZBsCrq4Dt6lXrZsul/AA==