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
- e2c87d0674f2da11b80af77c098441f6cd7dc5c6ecca0806f7140a169140e713
- request
- cb8db6bc7e97bf07adde0291323261cf41494bd1f6c193b25cd9a0b5f45edd8a
- transaction
- c947e004480bfe026a7e5ffd7b96d9a0934d360a3bb3763e48e187c0849645ebcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43113
the chainentry 43113
- sealed to the entry before
- 9f3bca5a99f5e4aac8485952c0ad4990d84124dc836e3607207c341b99ab2fdd
- this leaf
- 6889fc5e30762289590b001fcb06479ad1a934e48de1b53ee7c03e64921f0111
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QaqmpHywHooKxAg+JXw4sa9xQ1RZVygesWwAfwisNtpuAWTNM9o1bMwkXc/2fAc44eASIorAjdMUpTELLOk+Aw==