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
- e362cbd2b0fd1528f50f4b4e315c3af3e1b2b1a97682eb14815382aaf0f90df0
- request
- 46f6b379574406400a400b4761f17d9aae5bf3c181f0ee94ee2f5c3395179c07
- transaction
- 1ae69fd6287b18cff909eb7b017ac29df54d24c6e77ce0f65fada610eeb67c0ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66323
the chainentry 66323
- sealed to the entry before
- 0aa9894848f10371994e9f76ea9b77b9fdf97eee140f836532c74e3a4d1cac27
- this leaf
- ce798c5b6b8ea629af94fccfb34bd5b33d5e8f0983dc1d4f70e25f502eba7938
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VY4Iuoaeg3ujH1U6FAfB6rXyqWw+TQHFM6ePFbuzvlvnAX5Ocp0LeqWnwXpk3zAasK2xKXs+LfhJ9Ac+oz80BA==