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
- 1cdafe7bd4aabdd4fc94becb9501424569139812f56c552ec371d61d5b25b2d1
- request
- 2cc624ce0d589de0655118ae120cd5c505ae3fc32ac99933b8ea3d0d40c50a4c
- transaction
- 8e43ae5a649bacf031a57a0f75cae9c85a614d5677a05b265793d5711bc8e4e3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61018
the chainentry 61018
- sealed to the entry before
- 4d1fdf1259d26e954522311fd6a431c15386d073f1359e3ffc5035eb71ad2a61
- this leaf
- af0f5a00ec33dcdc8bc7f6d1e8a7e7d02a1f2c70fb761807a2014184f92774ba
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qvvz7174g+j0YVWdbEXOJLS/gmb79J+p7hRIyjTUTNnrOFhmpZIvelRJJt+uvDjc0lskc26sega4Y8uEbog/Cg==