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
- 59a1b344b73e36e1841d04302247d6db8828eba82b0b72e9a8007cd44367822e
- request
- 9a716840c4c95a818ee61c53ad8898949e73e6dca9e05e65a692385441324896
- transaction
- 71477612e2169043befbe5ea740fbd0639dab588aadd5125a621307bf85b4863computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66774
the chainentry 66774
- sealed to the entry before
- 391ec440c378ed1fd96087873556882969b89de00b94ccda441d7dced7f0c974
- this leaf
- b0a309fec60195e3bca082d3d87b80550bd57e83634baab197471462094b7da5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lMyzdvpnBD5LAV2uMwAJAQ+O1YXW4cGrJCzs7xEe4pHZB5VIdZDSC7qAijpYOCg/vgjJJ7XVHfvaqnRgWcb1Dw==