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
- 3a30eccd3b28081ed24bde3053a15d33ec1aba1709fa79075f156e65794848c6
- request
- 1924c56351829d4c9f77c548f224794c35e4c18fb105a3eaf8ebbec6c32982e8
- transaction
- f3f552d917988884d30a95393e601b5e60e5c82c8a7f338bd70eefb33350f575computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20481
the chainentry 20481
- sealed to the entry before
- 9d11adc2e44020677d9e806bd6d383abefa0544015e3f2f5bdc1aa9d7bf51527
- this leaf
- d988826fc50b9717142c33066d85b05d408851a3ec946a5cbaf0a6e09f7aaf69
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hGNFMIOotTAVeOLm47NyL8TJo0neWChtg9sHKbZMng4R5/PuTvtU04EBMoT/NP+c83fwWs/+c5YSL83szd9tCQ==