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
- 0a3804f69f091830331a24cfa44141396fcf16b860172b3ee8792202a4bb02bf
- request
- 59f140e297fc44efc0d1ce921f0403fca6cbcf67540110cf2646b13b9a4aec6c
- transaction
- 69c7d95b3fa03b765380d214e67e6c029a512f1541b0ca8ac8c0769949cd2ee2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22038
the chainentry 22038
- sealed to the entry before
- 53f00fb311f2f1f7d349f82ccc33cf1083ca62a5745b8a0fb09f02df4bf6d97b
- this leaf
- 8cdae7d9e00665211751d473e49e348d9c8ad8c01719b3c218c720fd73a0734c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qRQwOWmO3M6RvC4Qqn8cbNoftT694kziNnOscj9Oe6rI2cylRYNRANzkQKL/FHS/yHF+UQRLx9Ji2mdNssIJAw==