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
- b9b2330b9224b11428e87931e8d11039493f1fbc993d3c13d6bae2f1b3e4f7d9
- request
- 5fb6ed0a50d9138421e3223c3e2d5fa27d0777024a70e17e66c7a4e77e82327c
- transaction
- 58ccd08a482e660e5ec6a8738cd1f2754b0e803c131da1943e4de288302117becomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60220
the chainentry 60220
- sealed to the entry before
- ce7c986b2f1c0f5f95d41b1f069ec60762173036f29e12d835a0db8cbc3a8c1d
- this leaf
- 67e2227ccfa21316893d7aed804614caec7005eaeaf277f67769530f69f1e68c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LHaajTuCvJUu+JR3LK27Qjokn61cxj5HzdOsEtLAeaL6M7U+5LuuhnScOyzovRL8r5W6XLRZlZw41rg61ZCPAw==