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
- a8e1ad1bfc86be6667e38f07cca1093c04396cfc3c4c2d78884c413e4d7805a8
- request
- 9c2e3409f44d4ae4bbe6edcfbaefc141f3d949fdbe99b6566c5f35dec32cd873
- transaction
- 9382d6be55fcc206aa0f5a2a655c309521edaefbf4cb378206240e2486ce5a59computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21429
the chainentry 21429
- sealed to the entry before
- a05e77bc3ec427700d8975b465977eaf29624ee435821afa7cbcc3b538f17f64
- this leaf
- ce69819264593f454f0cf02c92936b2b16ae3620bf23c42cd0f304d8596cc378
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c+wYHkV9kb8/altR2L0a5T1z3TNX56pRjqJlXMjA++zxl9WfWMB67yzGRWTsXeSXABv8WYNMPiyYDLVvOoJ3AQ==