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
- 8367cffcdb369aae659047aaec4204ab4a5c514d079cab65be41d398d90d54d7
- request
- 7dadab8717cd31374beaa835dfdee05b594273d21fa31be7f37fa7c4543e3e0d
- transaction
- ece932d407ede6896305d86dc2a7319f29fb2dcf61d13a2751a3cdc5775c2bc5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61710
the chainentry 61710
- sealed to the entry before
- 72a2cf4cc785d8a8540c23ab9d0726830d4cbec3a8eda4919e21635a55962f29
- this leaf
- 9bfcc46bdd6ca56d908ae62b929a488deb204494ced987b5268c501104bfa59a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MGBue/wvWaq6anBLfTf3zT7gau6EI1rEGQGQrW1ACW4GA1YxwH6esvnHImGW2rJjmjSlaNkLWftkIufQOF1lAw==