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
- 23af4b5f43fa4dc87ad7fc7ecfd72cb635253578c9a3a947f507325841a48b4a
- request
- bd2ff356f3366fc11302f3af78124ecb6386c4f85e5123b0702a5621f137d057
- transaction
- 566a020a260fc2e7ffc1d70ad21f8e11c36d9d7c6af58f30b32e55786ec7e50ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60809
the chainentry 60809
- sealed to the entry before
- 82d6e3946ee6957bdc519c44a85498123b944b74301782e44058ca8e759f56e0
- this leaf
- 82a9b52d7f96680211a8ea6b10c52cc7103e3dbc4916da4b8f35a77af04d52ba
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MU9qTIsvA7HuBTwg+j0GZvR48Zpn+f9eSp7A3aAodi228jF16mO6fCEimdvLeflUFTe4D25kJIpNLYYCkE6HBA==