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
- 0e279564e8caaab8960a1c9029909bc94ae136b1bc6dfebaf80010e466a11fe3
- request
- 0c8c14013eea72061569a92e4f670ca8157783da5a1f57790bccc7d365e04466
- transaction
- bb2ea3180886156bd8e2152d2b54623772088da60f9a37f7d05a866f1cc52244computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17175
the chainentry 17175
- sealed to the entry before
- c0773d6635d5900791c6c8d81a92875af93a0617366c67692f7417712d239065
- this leaf
- a9eef26d188d003ac1cc7033dea92ffb8acabdb96784c90bface5a42d6f9a4fe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AUGosIcMnwnPIoy1IcSKb5uEC8hGouIZ/SpwevnlSnw9A0PV+1ezvAIGSK5jF0KeKxIqA4OrejL5QhWIOAz9Aw==