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
- 7d90dd1995223d02ff7a18eb0b91985eb4ebcb7b6ba0fbd22172b6cf1fa1574a
- request
- cd5ae99aeb51d6947c07cab17b59b1eee398763611c81b54dbed42b581391967
- transaction
- 610f700112a2f1404e11e67ce48c3a0669c00b6dcee13b0b2024bceef156c106computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63836
the chainentry 63836
- sealed to the entry before
- 0a92e1ccb43e2e26fabe0783a44d238dfdc87597b790133910a02b16c44e032c
- this leaf
- 1798f970525b6927a89786d57d5f60618278d615bb227684c8dd12773ea29b31
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cdqWuHIDiOaKJ2tHqgkozvkaG3M70pJZiIt9YYj0zhGbkZHmccpPMRwmtztkfW6loLR5MgHc8aOmuyNV0LV7CQ==