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
- f1aef14e7b5cd16035c91ff8f168cc84609078a95b126a35306fd66edf99e083
- request
- af766d392299b130b58c661796a72718710a9651202a08bd789acdddf41b9a25
- transaction
- 91af08087b0e55f9ccabec3883d0fb625862c2762c87a7802c80af06d28db512computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10037
the chainentry 10037
- sealed to the entry before
- 22ed6c343b4960755129872b80a77f9d5ce97eb80636d4a62b3779a8ff23872f
- this leaf
- 6277440f027ff5e60b17089c71490046c332af80208264a9be9020f159b9cc71
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- la1Xxuc0MHcOMKiHUYUi0UeJlR9/cKugksX0LrkIjDmYjigC4Z0SzGm3+Yxv46EUmITXVnWyFyGu35uslDWqDg==