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
- ce5eb33f18570d260d76b7173d1a5d9ac2d81858721aa0802a5c27c185137c06
- request
- 5ffcd4d0ac424952c796704557d79f5c1475e2ed33d59ba4659b7bb152bcebf1
- transaction
- 7bfaafb8c85710d8b304816d92deb828be61f1d1e99ec18ecf75ff0b82413715computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74050
the chainentry 74050
- sealed to the entry before
- 0c5ddbd86d6de7ded1eb473f72f0fd48ccb55922c946c51fb15cf3678824a4bc
- this leaf
- 0e1597a0b1c91ce316918fc7921041cea53f0c71243281812d516793bcaffdf3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0RdUQVn6QluAMTrN8njUT/w49mX0XlrWHwHUA4Q14o4L0nTwUVy2ziKDEH1ux0jcUYg1AiCA3jspgEeEod/WDQ==