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
- a02eb21733011020e962614ab1d9f82b3f8dbf9f6b6f1eb56fcbc26f5a4947db
- request
- 7a25551904a0dea9d21aa6cba15204ffe218955bc0382be8c5e5371cf7af0a3a
- transaction
- ae95f6a7f6f594a83fc0bce25cccc67f6ed2cb385a46784953715259b1b76675computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3685
the chainentry 3685
- sealed to the entry before
- 549c3f3cd72c86d06502e1048233263bc2d95bb038b26369d94e3614add3eb16
- this leaf
- 996ce3f7a3e7993e134bfb11995b69ddaf35813556cac2afa693ccfaaf7ceac5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /B0sWk6JxnC2ZKQWJgfmj+dm3cUBz5z8VXoZqToWSDSzx63LKUV1NsYHPlQ+6aDW6esicXCkEwkCIwFmql22DQ==