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
- bcd1c89090939dd8d89ac552103e2e34de679384e46869f9256a7407e710f3ae
- request
- e0a27baca7ea43eeada3e3d56cad0d0bb9c3a2ceec91e23c91f7b42cd3a5da91
- transaction
- 0ae926285309851ea94ffc6171e1aff1d40cd0a1e2ac4438972d41460ed87e3bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58247
the chainentry 58247
- sealed to the entry before
- 13a096d634702763ac8e876468c50b0536b218fb757e4e3e5758274acdfb7b5d
- this leaf
- a8ec77a6851ad3ca020bca27e950353c3591e290e4b571c4c6213f8fc4c3e799
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JkalGH7xjCmduAudQx+ThUl5tJ4Nx248a0zGRTbFnacsgGuAYH2oUKfpNkYYFAOrfT9pbpBNFesl8JGOiLQQCg==