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
- 6997467cb585fac48a574a0a23755169aa82ab5c4385d1dd49bf563b6a3e750a
- request
- adf3cb1cd497749c09465ed3a65fdbfa4ff92aefa2522157a7ef32d3ef8995b7
- transaction
- a23176c709a2b420f035e53a02558e91ff8fd6a8ec0036fea6f9ea298eea1eb4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1400
the chainentry 1400
- sealed to the entry before
- f9720c96bbb1c629bab6b8d460de14602fcff715e6fae1d77701e0478167ca66
- this leaf
- 101a2b1105f2422f31a15326e8260a1a68a2ea72d353fc232ee0575ea8d026bc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- otG/dltuZs/lJcAW3GRB/5khiEtr9F1FydnbeUb3rHzftMVy8f5XUt/rBzUUi3vrAzGx5sR74K0iUpynCDq/Dg==