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
- cc694728a82ec0f5291c7ebd4c1585970d24c7a28a8cad909085e7cfddaf0f6d
- request
- fa117d43c059ae8b1f8bf32f493b01a1f0a9b0b85781515e84d0caa0a92b8a26
- transaction
- 8a944fd40c82a7a42168d5138fd1c8de13ed4711bdb8d6ec67288ab340d68522computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55203
the chainentry 55203
- sealed to the entry before
- ca7c7a83604b60f4272f894e93f180af0094f78bb71df8d2ede57c016b08228f
- this leaf
- 057a103a5fd87390217392bc1ef9bf923c3d2e0131dc57b399c61474703b4bb7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KelU2xtftGRXwHHxvzd3JQSPlL3mMf3JqJBmcJS4FcEeg8sQET4g2ScgcwyaZavHKBFhy9PmwJVUjnxZw+0XAg==