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
- c5f2b75656347da6c33b5cce4f171e8fd2e3ac3196676ee09cd76376d6172fdd
- request
- 662fc9c2207a68ab9863c5c6eda34880c2b40ec07b86c0227112c86d1c61bf38
- transaction
- 0cecac9ab07680733ff5c2c613e1afbe98c9f25bb5160368a31a29cb0c3f9769computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16127
the chainentry 16127
- sealed to the entry before
- dc4fd949347909ac29739b65227ab895fec6aa95aa6f382fed76065a04d0d79c
- this leaf
- 0124c61796042c766a436eb9272de177a82c8156898af9003d96def9658fb01b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UAaHbxELjXChdFo6KnIScTnzofUQEvQA58dWVTxv3cz7AX5UPwnjqB+kU1Rkp56U96EO7hpxWxY/dGOYWz2HCQ==