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
- 69d77d920bde2e1e0dc24b04cc16516bec56467958cb69fe9fbf708862371319
- request
- 7cb2a54d9fecf3cc332f919ad6be41d0440a59c4f60ee72462a6676907ba6224
- transaction
- 4afe45dde9b7dc4c3b93ad597990a815781301960ecb3d51c7f0123367679e0ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65774
the chainentry 65774
- sealed to the entry before
- 5baff57d9e824db4fb499c17e9a7969c99e8ef78e7ea413bbc3d84ee1992329a
- this leaf
- 46d9cd0af1727f95b99b7771b606aa582e07d7b25ca07970ea60d94de5ebe2d6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- A13RoXHP498aO7Y+cRgGUuQ+QfvHXip58/F+cclB2iTMIDxQRH8Re/coTIJeZmxNBg9pkEeGAmfVKN4iBDP+AA==