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
- 756a961d3fe449d5849313bef9d9d52525a4d531607856fa14b9877ba7d3ca19
- request
- b61c208b1036b213a1ae091ed36c8e8d7ed9dac0d5c5210b8f51b4defb1d7f96
- transaction
- f785af044955030342c520b98d7fae0848be04581bad87a8e8f86c840fcc150ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2455
the chainentry 2455
- sealed to the entry before
- 1a8d64b92094607ea761d87fe81ad5a8bab6b4b70cf6083500bbb10e4d731229
- this leaf
- a53db86c670154b536a843ab140eb5840b84231ba1001651875db5f7ab380c7b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- n2MUOIR6fAMZeMTL7KC99Itm2CkdcbDxaDQXb9vBTEH4j47z7TRnBgr2dsPhkfGoNd3Ot7335NG+TEEXrBahCQ==