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
- e4c62652b169f5cafe56c4b64cfe4f2a336081000c468c0a257672b3a290d28c
- request
- e1bffe6bdd7f39d57e06329a7fe9b2163f19d83b919b061cd2fd82afac1dcd95
- transaction
- 2249aa9f5f7416025a24f063a267a6567a2bfa0509625b842cfb76ddb214dcc6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2175
the chainentry 2175
- sealed to the entry before
- 2d1a7ef19abf128b90a89c98ba0b6cf3c9a1a2d96f8612a8cf9ccc5f704b3744
- this leaf
- bfa892436d8d0ff531019fed5d8b7a33775ac65ec5c5e545597429f733d36ad3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JX8gEhcFfWYixzLPE7GEuuKLHyTupl3wNYHzZ8OBQtfLsctA5I0OOcDkpLh7MVcQ4W0Ot+gCzLEFeexlcGQoBQ==