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
- 5c54c5fd37a2cf0744925e90cd5ab813c243bb90653c1a3d64e2a72501988624
- request
- 6e52cd9d98ffd488b96cad63f7b1962547c390e851522c0134ec24886e558441
- transaction
- 46f035e1b7986c4c8899ece5c0cfafeb5ec46384031003249d304e6aa6bd04fecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33631
the chainentry 33631
- sealed to the entry before
- 6e8cba4b1bfc5815b4c87ebe703eb407de922cd3e636a9f1f929679a3bc0daf5
- this leaf
- f1fc5fa9194be0bce71a4eab3be19dc040578fb75a5c58a9d1c93045482beee4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cInc/k18HH8/Je1XKCmGzPmq5LMB7L7ZvqeMbamGXWiwneHxFEYyyU3yKOmTPYvX2IHJoaHmgJ2cJTWebCZXBg==