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
- b6d371a210f7ce8bc25ef95a0011806c769e28edc39427a9199cba1db19148e7
- request
- 66cf0a646d8ae32673eddb0a888c34d5b61e84f246a9e128e8567d2f86d7efbf
- transaction
- 861b936f7c2fb5bcd1d68b81e12652120e32d0e9cfba9d0fbe6050a04577b32ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43170
the chainentry 43170
- sealed to the entry before
- 3b841126d8687bd27ec1c6cf3045d0f92117a849d61ef3b4d5bfe7fa0c306f5e
- this leaf
- 13dad93868fffe520c3cf4621fa9e8228c692ba6f4a9b215aa789188f859611b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3vlCvZh1yjG9cPZytXo2TqsfSgqeKSWvpGqUwyT8mIZQhBz8a92v+Hgx5Xt9oODwKnjs4mxX0+ReCVCfO05nCg==