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
- be472dee05bb72bd28910e4df59258b910a1e86492c6c285bff229054a559d97
- request
- f82c33077f3a28df3184d051e8519b1b9b0072cd386e50505d96756b9607a9c6
- transaction
- 4328795559c24c0793e18498342978edac14db6021c694fee5670005726ef7b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28378
the chainentry 28378
- sealed to the entry before
- 59f9c3f99c75ec9001923e84c8cc5c23c7835c9c1310378accb06d94a3d9e692
- this leaf
- 1a696ab3350bd96f14901dc04edb1cfa03d5e11815b39169c1fd550144244648
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DF7lFa4dxZYI/Hb+YSGXeaYbB/5EXTZbf76zUbhlfKIfoQtjssH2boqD8g4zkvvOvWxjvYjfi3MMC0NnnoOxDg==