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
- b28131df81eb28c9f06d28d83cf6555a0ffe1c54f3b5dcc448d6c45c34f3f59c
- request
- ef5352c0f8f0b70c4e2fa3ba90c8b7a30c103eda34d7f93c8cd5709bd73b6479
- transaction
- 453417fe5a6d04a98b4aec3174e659fa0d4b7af5ac5c16b460f10163278d5f8ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8068
the chainentry 8068
- sealed to the entry before
- 0e5bdd82937945fda91fd3a9d0df5281ee673756d543ffa7b9a0e0f9c4005e2a
- this leaf
- 2988c37560815b1b667d1a2eaf2ca6ff70aa4d59c55aabc845e671aa2d15bd1f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ps2JexZTMsS9rPNNGYStV/BejVgo61AQhX/8Sq9f2ruPOkyRhlb+QqtFGSZLejVigSZ8Ew7bOWBDzVRVZshvBw==