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
- 8fbc7b24fa35a499dc1bc77bc09a730045d2789a5eba77821d47470f98d8f590
- request
- 921a98e318e263f2315d089ffa2031ae53248d2bf4f8cdf479f696b024ae231c
- transaction
- f7ee1989ba7a99aea8959096a6f2e4bd161b398f664071b30bcf690f6daee3c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12160
the chainentry 12160
- sealed to the entry before
- 718a7137235079eebaf1f6b756178d18400342c2f71bc2468042375b4af03c11
- this leaf
- dfde15be29f01d6eae450b62b76ea3be1149ffbb0d85f873628fe6fcfa5d47c5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fU/ddcoTjaptECFgciftTSUO/4OlFzQ4mBjoPe31gO4NmIH7k8TNs64ATqKi3qpdWu/5wEfi0yvd+04IkC97Aw==