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
- b9c5a0d26a0e6740b02656aafe05f017341258568a5c5e842507d680625218fb
- request
- 9d56760f5e2b187b4290bb405c3b3509181aaffa4be5418daf5f0fb0a686946e
- transaction
- 24a2b69d28e23899422b37418c121b0017114761fe3203ba70e633c3950411becomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75844
the chainentry 75844
- sealed to the entry before
- 0ff13bab552cb1dc39b68417231d6c00193272386a30edc5e5a8cff13b014475
- this leaf
- 15543b5c4e94ef976b14b810b9ad9827d71cd1621e17e1f06c3369a421271536
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wjNEyA270V3cwisuQ9Hau/tsWnxV6rjzJsVImYvRjl53FPalOdkk789kq/fCUgsPsvPEVgn2JAoLr2l3Ll7cAA==