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
- 4e684715aa9ffe384359e7363c9b8c77d4fccb6e02dc8b7d15c62bcb9fdae521
- request
- e476243bc2a438c7e0f60559a053daf56bb8f1565500997ba76cc30d3b0c09a3
- transaction
- 10d9b6b08471a3f24586a9b380968e78e33cee53fcd5de7e8bf2c819e09306afcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1540
the chainentry 1540
- sealed to the entry before
- b27e1fec21063fb9cf61f95fc32564969ff68b3d57e6004b11a74de1091fb894
- this leaf
- b5a5feff50a8faed30aefc2499f6f27f935c25b681bd8d9a595f4fcec809617b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yH1OfYEekpMGQ9Z7JigLHxqIR1RVg1G6P6kcv7peZyusvPH9OhG29G6hfKVGbbfFjqH7MH2e8vXvSWzAv/vUDg==