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
- 7c7883c662e0f65d3b1d96a19788266c501e46a8394cc53e80917b49bfb2c0d9
- request
- 1d8b387247635690ba1cc669706e3630cdcbf62019b39839bd9569e96036e1d5
- transaction
- 6830fda3faf0e8d08ffdbbc07af25deefe4277f0d00de49b22411ee690661a6dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20017
the chainentry 20017
- sealed to the entry before
- 49f2ccb3f1bcd0ee0932dd7505480fc38b6842306182b694751dbffbf6cfca5f
- this leaf
- f150c223ee92c01269d4583aa04bae0dc055baed406e60ddb9415281539f2b3f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hrswse03C45Rruiksvhr2mOGTA6/2PXOjBaW4zMaRL3Nj1sqtdhmtXkKDSYctScn70oymRQd8AtmoWCwapHTDQ==