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
- ff0f884569604dc94c98d5fff7dccc607864d29dd304ffdbebe72798f6267e71
- request
- 1a3d8e879c9393300d55f612e337fbbe140b8528e878d67fd24b257119bb217d
- transaction
- db5f82b7907c41ef4552f19548a87c67414d259fccf4e32f11414ff09bb85a6dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66035
the chainentry 66035
- sealed to the entry before
- 452613b1fcbdec74b104646303b32a4d11ef21e54ff3e0e9b0ed0818a4ff5c22
- this leaf
- 39bff954c7ee4a4683e411917fde342c99f56857c5b6deb9931446d879c764fa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oHM7YkmJ6AyTKC0itrkODFyTJovGQu9tnbhNZYtO9fG11QE1XXi8KWLu1RwzdTN2lSzqlx634CBgVpFJ1f1lBQ==