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
- 35346ddf3ec9237abfc644949dc9700a75963888235a1de86c7114484ca625b4
- request
- f48ca9b261cd51256b793ceb3654c45d6ee226f9b92a49ed34fb2b6ca908bfca
- transaction
- 415f1bbbd9962a8a0579ac3ba9eb4c82c91123fd1b366747215267a7938c2baecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77788
the chainentry 77788
- sealed to the entry before
- ceff79eabc11fe23bb6d8ad1484d8bfc758f4c91d66b5087a8657a6d327d01ef
- this leaf
- c801fefd6f669f39c43734a2b2df50fdf35775ab22f5e5fd2173ef5b393711fb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- n8vArWMmNsuBlM1D5R5qoHk2OhjrW51dgmNu1z9B+z/mmiqLMu0V7sefJKEj7ZZjxyFmRGYbZyT1ZqyGWf72BQ==