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
- 83ae08cbc0605ad4cfc755d4325bac573fa572d6e674b1dd69b863123bd3770e
- request
- c0746137cb815026c3e337acffbb56829378a1b806af9a09f440737eadcd9353
- transaction
- 04fa02bf6a1675a6806744f58868de31a87b401ae87c5da69c7284ae5f4e25d4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51935
the chainentry 51935
- sealed to the entry before
- e4106d64220437d1cbd55f99325a88045573bb6f31bef86923698e96b8e56e43
- this leaf
- 5f2748c307fe118ce3fd5899d4e5d600e6a2fe790d59461bb619ab176b49e458
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NZxePPWda+Sq8O3S53zJ/tN2FVTFWowvseAk7ocZ9cl0EaZ20YvnaZMEu4nR/0z0jmO+XKqwE/HD4N93u9u4AQ==