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
- 28b0dfe461f3e264961e8fd2988be189d969058e456c921db4f59b55b27a497a
- request
- 9d71ae3b0ba0cb83e44bcb4c7abb376f4b1300e41e9a2f8cf3696caa2669ccee
- transaction
- 7507f9c3a070d5e9758a16077a2d8bdbc9d7cd2f0af50d023bcf089e6367d8f1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75886
the chainentry 75886
- sealed to the entry before
- 09c76f154e36a054468f79c4ffca6b9a0deb6b2436e4be4b8d686d640b09cab0
- this leaf
- b3fb6aaa84caa16cbf91690e26c84462fdd21fa4c3ecd661cde7e987f81e2ed3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- T27Vod+kC9ldqBd+i5B++3847EzLa5Pqg26NHP1E0AQhrgQMzU87n6rRbgVqjDlB+Tb27Y6Hr/g69t9hmfuPBQ==