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
- 9e063fc525702a158ca80f0291fbb360b83bf787554f7d9bb5f446dd480ce934
- request
- c16c5175c052abf3b4a440fc4d10400502a530f70c8e84d983667163efeee6aa
- transaction
- d1363c32be31ca11544d36803fe51588ee235f859a6ce10a42e80ba773b15137computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1585
the chainentry 1585
- sealed to the entry before
- cc1906b112ea06593916db1e33eaf4c4fabe1a48f32bec5ffb2b22edd540b142
- this leaf
- 800326e29cb3898f3abf3e5a389177e90f06b7886e0c86c416580be4de96f530
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IscPtLm/ZFUkzibgHuvxKgJeJTzl0CuvCtQbMiKX6J6uHTHUqHEFBWZN+onCdtYc53dB4ScMghCJ+FC+Z7c5Bw==