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
- 066ebcd74cc4d32853799841cadf5daf53c9647294adf6ab54a876a4080b8e43
- request
- 551625e6522ee113167540635c123fc8bd912fc6eb5394127bfd3bfa879be23f
- transaction
- c5eaaddccccde055086d7d6d341272aba46f5a38e66771d8cddfb29e6d8d9b16computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33106
the chainentry 33106
- sealed to the entry before
- 94e461e59d312f32715f45b49e01fda7bfd6fdec43d90582aea33b1f1e752571
- this leaf
- 2a82d6ff59ab11eacb334468e933372dfe8f8c32518a624d5048b0c68a08312b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PCoE1f2IGsGLOghLMcPzzxQjcoFsgw4hFzh8jkQGD4fJ1HssMPHRtB/PyXPWPbWR9BaksqOp+6O+33wIyeFrCA==