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
- 0de930ec1d12ae09e17b07ab0769d16b41fac02531c50f114be9ef430218a330
- request
- ce1be64155164cc21e186fba038cd0fe75eeb7164f1ca55205bcd8ef54042ad3
- transaction
- 40428b64e7bea0df8f0d5cfc508dac60c1af2b136c77498ae20397f6631d9663computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66002
the chainentry 66002
- sealed to the entry before
- d2ca70becc1cb14daa3e4ef584d5df2efb0a3af78a610c850b124efef0a8883b
- this leaf
- e0bd08e36c0aa6ffafd92421fb38bc4ff313ee908615283c6c8e2ab7f6a93c5d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EVqesjLgW04qvCi88trcUArx8wQZNite9TqgkVs0L/tRx6q5KATvveEnptTLb8z//siM8n+pjRR3Q7OR1ac0Cg==