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
- 86ead3943c99b8c6e4b5bb6849fd2bd015d5877cae0febb9fb36bafd71f568ba
- request
- 79dcd7fd7e57b1647032cd06011ffc6300d8dcdf2e75abaf7763987208be1a02
- transaction
- 40b7c151bf08aeaddbc05258e46fe6a3b750c548c90e63e58d222efa7f9ff423computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3995
the chainentry 3995
- sealed to the entry before
- 87ce41793f962602fe79f1b40f960ed5a038bd60618aec1d4fd5ce270d8da86d
- this leaf
- 6f0a7d998cabbbf39d86089b63753865347451e8aa2a0e7753a8ef9b8d194296
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EGCqD2CBdvi/uj2JITHGacGgU5c0Ad+OnmrYOk1zy0QcmJIUEDctx83eO2VJOkfLkYFCicQgu1kEep3fX8giCg==