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
- 9688a54db05bb195a52c2ad1354f42d482b32c80a934a5bcf2027e24f0ac7a9e
- request
- a0f190475634fb20f4218a07a7c90981481bdc3abb136de9f59b2a34be2adfa2
- transaction
- 76c9aa4adac1a167e22358876e668b5cf260d15b7e00634661aabd8867475925computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53191
the chainentry 53191
- sealed to the entry before
- 0060d67f0c5d05a1288a129016bc91230d10e618e5a011b07a845da56e97dd2d
- this leaf
- 45691ef4359d8c4b0f35157009095a9830cac478dd2ee5352ffb604446066a46
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fSCCniE9XsGvGPTAe15V0kKaLB7TTNLpioXoAnkwxhxNL+Exzk293fpvQcZTnLUEzvyR3pQLY/PMa+ol33mxBw==