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
- e38de4247aef80bd3279fe0e5ebffb7a60fe5556db796f0789de65c0ce2b4c28
- request
- ce86b8d6bef5be4a0ef2cc4f1741fc0daec7d658970e82ed05e14c5eca1f0c02
- transaction
- 26f6f28665b2f541d5df0d178457e0cb100a61a2044c9ce9aaa6b15170331ab7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62207
the chainentry 62207
- sealed to the entry before
- e5c6403277ff35bb25210fb5b5fdacc2a73adc5b17d8520549772c35f30aceef
- this leaf
- f1d23b869dbc9fbcab85926c913ccc5c689f44d061756a1ba4df55bc8e0b4018
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SQ415lwC2s+4PD6EYPE0AXZPK6gjKFm5kml/LYBUgWmsW3wNDYLg5Uo6q6fUPZbA2VQxCmt4/9/WL4jr1UGQCw==