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
- a71c25fde4c5a9a8b224e4e8c4b4e94341021718158aa2d98fe6fe4bb1011e97
- request
- 958595ea8ecb1e91af4f59e9d459b0674f274e73f1601db7b82c3b52f9096a6f
- transaction
- 302b1188fa951565a824bc654bc17d29a4abf4c2b9aa93940ad61ae449be96d6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42045
the chainentry 42045
- sealed to the entry before
- f07de1e70fd305ebdf6c1ddbdd35e2ae935de3f24b24b96217dc440fc03a848a
- this leaf
- 102bdcb4267c7720c0b76141ba1b6919b212aa245f8c31c2b948e5259229eb33
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qqctVoAfyuo756nLppK1CaCha8dcSn62eerIj/raV5sKm9RoOtHLB46CeNPjFFVfXy2Wiw1nezcXotgKXMRrDQ==