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
- acece7385b129c8c6ba21ceca26305d6e1d916c60535806453a7104dfd919173
- request
- f8e85636a608e52e0f379d2035b9b9fad3fed383af612337bda3055e69bdadeb
- transaction
- 2fbbaa5ef4779a38c5af30015ece5a7face8088d5956d0c6293b37c52792bf32computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31724
the chainentry 31724
- sealed to the entry before
- b73088f81ff3d845ef88a9b19d783d6752093c8739fe03aa7e7e997160378ad5
- this leaf
- 90860e0996414e85f170f4d72cf0d7e375adffb4f9c230f36a1d4e36fcf07ec6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PGtCBNtwcGR3HZl8NkLrjeYUH1um6+6aAJr3Ik3vK6aSu6LCpFsl8zGDsC29rhfzGHSMQtMMf8MCNaW8ZyPxBQ==