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
- fabcac09d80610a5b2125954eb4ed3667ca07c0e19918815a42fd06d1406f126
- request
- 9bc9009a9235cb319f6e1efaa72ae00912025ff77cd18938f2c66edd7d899872
- transaction
- d2b07a534b317ae7850b0525f3cf8fe42ed510092287c3d4ab02fabd6d3f89adcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11939
the chainentry 11939
- sealed to the entry before
- e2470733ddc8168e5ee56bc9ff01089a64c3ff51b8a39c4b72dfb5423d1823a1
- this leaf
- f29396362b44e38894358baaa16ddfd0dcdbf194edde82fc0e2dc17496d42493
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UJaX0xlrrDoAgRQvhvIzoXjoKUD7hMJBevKzAZfMYMs9LDawLiXBFgTCMF7tNmVrp/+JUTiKuXB8ilcym0q5AA==