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
- f9116da19a6f9c0776adde94ca11c1ece9cb590e0809391552663d878a9a404f
- request
- 5ed15e1be5c3c962f66424cd4c5904692dc0d4de6077f0efdb848e035bd130f1
- transaction
- 18a7698adece1525bf28e32a845ae7087dfcff951ba8b8ce3efd989115ae2172computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2350
the chainentry 2350
- sealed to the entry before
- d2a21eecab9d7a80de1279d7ff85a00837a748b95228793394d779dabefeaf81
- this leaf
- bed6cb7d2b8523b2b3432f7ef0e86f0425ff09cbae32a0b8d33c551bba5daf5d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- q5jBoLljVwuHC6j3fsu7SFZDfoRuNp28VMGZpXYCeFppPFnxGc6XfFRi5MosU3upYJUgGwFAA1Itsidnb9n+Cw==