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
- eb0c82bff78339c406f4786aa25c0415b1b0987b98575c0dac80460e00871df9
- request
- 3a87ff29a0f66a06646530584217a696610d7026bcc65e9e3383e6a336871d58
- transaction
- 593e062e80bd6c2cc03674cb1fb9c8819cf1091196d4ba81c810189f8e2b547dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46815
the chainentry 46815
- sealed to the entry before
- a5ba6f3199e776f19d366a62f96c3816217080cf068dec15cef9c588f50fa7eb
- this leaf
- 85f34b9e4daa9befcc02410749e9a7de93e2511d957e2b4828cc3e1ab97e360e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v7PY5VH5kp54ONer+mR1jRTsaZulrzCarHpXOpsnxfqub1JA7+l8MMsWfEPmFtCbTh9y7zw5ITVROlKEYMYVAA==