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
- 313c54d0918b949b49b840ff7809520562557849902b4fa54181d49bce9ea84f
- request
- af723354e7a3a8f7f492582e88f89575fbf052cc62c8bc9e69e3ed021c857ad3
- transaction
- 252e5d9e763ab07a5455294afe650d449585541a20100838d6c01ce6ab373909computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73876
the chainentry 73876
- sealed to the entry before
- e681a79bd8468c21001e1d439f40445b700c472407339ed094c4fb6cbb4ef104
- this leaf
- 870cbe2954fe877a032e91d5bbb527d507908036ae1b9b992e30c9a8380588b6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EMKseIHxnctIg+M89fRBRo2cHa3ZkuSIRX+dzwoq6oTFdvDm0zT+HBY+3IBSnZY06NS+VDt4CkAOCi7k5ZxMDw==