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
- b66ac96fd35c626767fab5b9a054b9e5fc0f46c9471376deedf618c3568669a9
- request
- 0d2cb1727ee91d4cfaa9276b9930bc56a0857abe6953cbf26e0d041b1b9a96a0
- transaction
- a0d688a3d19d415a70bb6db54d46827af45c8ebe81c8ebbe5ebaad533aeb09d5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 486
the chainentry 486
- sealed to the entry before
- ffd3115f63ed340127c8d064f3318fca801b1d2b4198d51a3a11a37e2854d783
- this leaf
- c2063fa19d6a7b521fbf287ad8fd8213b1bcc631b63580aae86a8db2459624ed
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /7RvGKLPr30h711lFsRi/wj4T1RxtV8WZC19H688OEoQ8NJgNAB7Wk6+FFOEWepNteL6EcRP9xljKiJD35YfBA==