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
- a68f773fcbbe419f0930cf21d29030155905f1740d7d72836d8fa0f7ab8bf09c
- request
- 80062836b9a342f8c7bd8eed5b0c17284bf2b7b9996eeedc76b3f31af037fd89
- transaction
- 9389da4179d8c8249091c57a6aa7b2549096d2b9e3b6b589518f9d7f62b1fb84computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50123
the chainentry 50123
- sealed to the entry before
- e7c51122bf733188f3267a5a2228ad2622b48548678bcf1c0f8d949aff499252
- this leaf
- a8e4962b66d6769c310d0e3aecfd1a84e15ed7c6a20a9b730ef01784d73e3379
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- x88HiN+GiMZr/1Un4ZtoCYLRpMcKZ97PztlUZwyvzYcv6fJiGMTwIAkwMOXZTWRJ4aarI2H4lyDzLDWR+m39AQ==