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
- 89ff2ab726aa05833aa765649064be708284531ec8e20601c0860bfb9c5c1ef9
- request
- 8049a111087fa37a830927703d3785cfa5bd6a6d6d5dfd5488dd9a42ee4fd1ef
- transaction
- 64e54b2467080ad4abf0da2045362608fa4a7fca7ed0c5a4a967f07884dc104ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3569
the chainentry 3569
- sealed to the entry before
- e47262201b91c16ea66049cb3996a1c3d6ea9e1667328690d00ae31763a9f790
- this leaf
- 8675b921539dc6673bef9f65788dba25882deeada7611220807213e222e74dba
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mrWKgGm7H4m+7Vg6DXvoonsjj7Eabj8I5EXncE0PtE+qMbwgDl8JuC/YiQ4nMuZ+iD419ji2A7KcEVOjdPX8Dw==