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
- d7ad6db1fab968bec4db29531c5fcb2bf4ec147899a9afaebd541db983ffdd61
- request
- 77c67ca39d4af7ca61313f27ca7795ae321523cca04b815bd3f3bc9d583ef0f3
- transaction
- 074077abf6e2a033c61f7982c0a1a978d695dcf19edb988c3a9ddee337a4b48dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35906
the chainentry 35906
- sealed to the entry before
- e3df1e0a6ae3fdbf3ea3ab92d5650b2a9c771e83fb7e46ab52a0a71219e02b2a
- this leaf
- 18a9ee8173b507d3ca54c5eb95e2b8594a1b418c50baea6ba494f2480f6f64b8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PpCRYWh6Jvg+kRJNseYCqnV7fR9p9PGyXR31ALmKbNRkPLePyLiUMrMgvudRtLIliA9wJCc0rYNDD6x3lN9pBw==