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
- 371e05996732a9babde5b3957cf7c35394ba5f37f3e4b403c0e2df2dcddd6f9a
- request
- e96c23864f9d449208b816991a93cd29cad687020d3b3634c5ccad82650608ce
- transaction
- 8535197090a2de6ab7e672abcf642ba55b9ccaf4b117a75bc47e66ab347b6466computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17469
the chainentry 17469
- sealed to the entry before
- ab2c248f51b14a046248950304d6f0373c9d973552c5dda342692e3596ec697a
- this leaf
- d0735061c07808cf0d8d2ea5e25c569ff94d52d8f9be08f31d14370748af6514
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WutDnDsflsXVxFxWhfTkKEqBdkP9D8yDYDz3qrOaKfqcVAuS/HwPgUq/nVbOtOwePsfWP5byQQHi2W+uEyB4CA==