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
- a3346a35f669372cc0387636bc2dcf61f611b4099e3920987edd418bfc481a9c
- request
- 5a682dd645ed46555b15ee7093f100091ba4e01403b75ac5b31cef9c3f87e74e
- transaction
- 584b616d4b9c6c38bd1af3f4f3a4cc201d3484f4af08ff10b051fbdf008aed94computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45309
the chainentry 45309
- sealed to the entry before
- 16c0b3f84aafcae0adb25c980c45d6d104236fb9f075db837b7c9e536c699f47
- this leaf
- a4df55722720d3582dd52371f66f28ff38fdabd8aa7601ce3d6f060edb9a55a0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RM75t6iCILPjEBh6Qd8dO3G0lmWX1jgkEKcA4TS/uAkpvJuAtslnFBIDdBwu9HbxXAL4jQq92Z3APTyKCEicDg==