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
- a7b0782d887391a274146804aabd2bbd53bdaf666c1e4bd7b9faa0d598fb4855
- request
- 752409dcb16cd00945cad586cd6b5338365407e07abe49d658fcc03db639a3fe
- transaction
- 3f6eee7360a052adaff92d9b9678264a50a3805a4452fc05bdba726a9c3b0e08computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55163
the chainentry 55163
- sealed to the entry before
- f48403742d959f880206534040e121f365659c18ce496b0bfb1d2bfa0a3320fc
- this leaf
- 96efbb388e3975b5fddf9de4c50a7b84dc3384aa05bb2b9eda655c94e8d48faa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mmG/3/pa9Z2Kyf8MtX+NJ6H9erQfFjw68iUa7B6ZWORWnC/qwa1ujhwYfvKP6ay8HMIJcYRmrFYc6Cv3FJbhCA==