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
- 21044e71730f405d8fa297178f7fb7e888be8ea81febc752fd79822ef5681741
- request
- 2d75d170821c740350656efe42093cb7a05af00a53596e5faafe68b733f5d1b7
- transaction
- 0175c07ad00742d26d3bb1eef574ea7a09e9ae30a1ae4e34440d974262fca567computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50635
the chainentry 50635
- sealed to the entry before
- 5cdc3b76972fb919888936b6f953692c01899078643dc7bc89e536e96d79533a
- this leaf
- ecdc1f43c537a8b805f298d13d15fc3ee0c8856cada3784a1b2cb55a42f1f82c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6X3Ibs88+oeI9g4j/z0h5c49vzyYXOvGuxzttroyksJEWvcVNtgHnWGbP9Z588RuZ34bOsk4uac3pA5Ymjm+AA==