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
- 8378787dd9fa3099df8d02f891663b1e9dda9591f1749c31f82e684833e6e1c1
- request
- f8f227e351e90e4d3620b8df8b3176b645ff767c34c36b73b508b67f4c649eb5
- transaction
- 2505a9a8879498c9cc57a731a298e8993724e1a2780ba1a704114f200d3992a4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27830
the chainentry 27830
- sealed to the entry before
- 1535ff63a9fa125c8cf9664fae10cda64324c23658a4ea61e53d77184c91a20b
- this leaf
- 2c9600e05eff344db822c71633a5a537eb911b71b935264c19d5e7e5a46ba1e5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JC49irGWDxdvZ9bk64Qub6+c1Ln8f1+sqLKcHWR+omSlYv/He8DhgK7k8/ZyP7ZO4Kk0XxG9tyfgKQbdj6S6DQ==