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
- 7710a3bcf8f10f78f8c111866e531ba2f7f7d0a5064d65cf349a0fb5d8631e69
- request
- f68846e0d826c4f54cf0fdfc4eef0efff467dd383e82066b3047ed973a9e2a47
- transaction
- c2d88064a941e552f04d2ef4c10cce795c06b590aab67835664871b25417555ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46033
the chainentry 46033
- sealed to the entry before
- c9449b1bc3a01c0b1b5095b9e33f2006a0d8d31724f7037560cd8bafde66e656
- this leaf
- 80557406206b6b4d4beece4914971211ee77f75824ae109b1a4bbcfee4f8719d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oBgsQNb+vjvV56eXBR2KKdKeEFmHuFx6WE6KeYKKoS2ttkH0zZPdJFbPgWsMlKBmswbgKvYjfZxbP9f8i40aCA==