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
- 18046b3a52b60294949ba64ee8994c29f68bd0de1924037734f114d948f3d838
- request
- f922b307002fa12f1dbc180076e78ac429a1b1c71d3037c7e535498fa00e51dc
- transaction
- 04e8fd839fbcc5c2b840335e7df8187cf027f0301bf554be6c13b0531bde9e84computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2065
the chainentry 2065
- sealed to the entry before
- 87544958d648806d6718b26544e8e4d2670347946aa9e418076ab9123f9eeb22
- this leaf
- 89e27151d4ab060c01f95ccd2bc52bc9bfd7cd784c94068e23d6c3a6f5a9c39f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sDbyd/Di2MLHy2Ign1iEMaJGSvXbFiIocoyp2Wv4I4QBSSt7FrJPq4f1uIheZWS1EGmGHyluTbFDNMWPQdg/Dw==