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
- ff6692b7ef46a1fbf91b79c574b165f88ca368088ac21bd0ebba5717dfdc63d5
- request
- adf22d27805dd62cd0b0499c6fa5faec5f8a9e5a9f31b244436221f8446adcfb
- transaction
- a957830dfb41dd0bb8862791203f03b035b1e5d5815bbc7978ae5f233c3bbc3ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64197
the chainentry 64197
- sealed to the entry before
- cbe13ae2c7b72664929515d446155e59e758b0a66b92532da215f54060b3a265
- this leaf
- e8b506ecfe536fd2b481afcfb6e1001e129fee775c4c8a5f1546d5d71bd29728
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1km86LeBmFkjp30VJUGKrH963sNmHf061mEn5k3WItEQKW7qcfHIqn0NrQUFwbIwDffWhThzElK7jTx80ahyAw==