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
- 182e29745a5742990441cd7f33c2f029254c287522af823b5b750c935a76d1c8
- request
- 0c4d3a5d2199a8710de79882bf74a8a4d360e3003268b2258e22ab1d45e8dc91
- transaction
- 8c087086ddb9526a109ac96968e11650b94c3bd66a9e5b10d39cecacd7c91d9acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8429
the chainentry 8429
- sealed to the entry before
- c600130e9b51759fd8e4693778301242e09270494f9a873c33c609d55781e00e
- this leaf
- b8ac84edd634289328b483b1909af8334ef3eb2471c4447d775b5afb778bce1e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zq0ElGU3t1FR1WSE5RcDXN3AzZDa/JTbzCvYVxThbepCljRRjHzztx22bl7+GA6PU59AeZEorR7yNu5Xvhm8BA==