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
- 6310b8803f3f02ec6e947e41079058af3670089ee3b8e582ed0fc844e2fc7b2d
- request
- 86c127473a06170d921da1ed24e8fa9aee7633769ea76d35d065301c2c4d55af
- transaction
- 61a63c4f489793151236f3aafc9e2d059660edb7c6fa9494b314b76849949938computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53953
the chainentry 53953
- sealed to the entry before
- 64658f215ef08132ec848c54137804330d76709530ed9a9df84dfde74722d264
- this leaf
- 74a1cbbb4391c1782033b3042c9542e582bc32dbb2dbc688bbea326c61e10e38
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UG4Y59keFicj3H0apTsNijtEgODVlp9LEFyyE38WUM80pNA+w1tRWxrYZzquTrkS54hcwokKckH95YsyqRCfAA==