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
- 999c42d37c500d7caac983b780136675b9627efdcd949eaeedeca9a18b65ee5a
- request
- b93220f500200c1fa805fab3df0c859af07b53577c029b39ed3439c40834c0c8
- transaction
- 5d1348cb43336974a964c00e6413c2fc68b5e7c1e4a3c755871fbf6e1f57ecf7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28399
the chainentry 28399
- sealed to the entry before
- 2ec7001f37d5d70ea02bfb0d5ca376c79c2bb4a4c1cae2b9fa52201059996944
- this leaf
- 770cbd309542243af25cc44fadda89819071da58f96d4b492c1abec949c5ed10
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Coff9BAKnbpoziyYu/YhG5xq6H4mW677hGUCKi30DncKLrHtb3uOqez/VNZ8DarkDIJ4b//B0UH3P2iIHjPwBA==