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
- de4f5d5285f6f7f3446ffb1935695b846db363fe7160307f5fd6a30b48329a5d
- request
- 3535eb3c1bea0cdace3aa35df49cf14c5e6b5b339dd9356d074835c3cd77ce6a
- transaction
- 6f4d3c060e0031b7a6fc0886adb5059a0431ad1e309cd04a8944c455907b5236computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28943
the chainentry 28943
- sealed to the entry before
- 614a3b0888815df39a31201446e6215d63ec0c629d4ed70b645083811b8a7959
- this leaf
- e8e7c0da3e2f130f616b4018e1e26d56a2e996c8ae5ac1bae977f1b2e45423b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K0q/mrTOu1fLkpPa1Dm3lsVvU+m8qgvTqU3/recRqKJ9B75Zo+J3STu8dOfTN5jIzgK+HnZ+PkEPwlIgNHGiDA==