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
- 79b062c0e90da6eadf2395f8804710144b21097d4db0e6ff48f75d641d06e13f
- request
- e094f3a3a828f2f0832efba8c763691e7041cdbf147bda40ee7bb36d6676ff5d
- transaction
- 89a4863b2a1cace0b112eb0570e7ff55cfdc7e8e7f446b5f997483faf57158b0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76810
the chainentry 76810
- sealed to the entry before
- 1b08db1478ab74a50c347ca87b8912ffc1fe9fb057edbc966df7ad0b198db652
- this leaf
- 9b4a07007bf6ce2f6ca4a9f7d2569b7df6e7e9badb4e62668973532df8279e29
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hgrbjF98WTb2fWMDAZggXCGxdU98+Om+cznJeYoiP5WEX5uMv4Tf6voobrhEv+JDnKAvWBMa4K5jGD935GuTAA==