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
- 19dd0bec04ebd4389a44430f08cec2713f542b1d44c6a43ac1427414fb3cc96d
- request
- deabf9ad636409eb33c805dfe9f4f86866d9e547d184cdef8e23c0c0c43f5f00
- transaction
- 10c1f38fc80ea96e3352207529063e0ca81cb74096c4813ba58a950825db87cccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67204
the chainentry 67204
- sealed to the entry before
- c2ee9acd08d9832be8eb7db5b94aa1bad8004dd3e8a5626d23f1461779bd2eb9
- this leaf
- abc0d049c8af017cc5dd473f599d1f2b41951b1181928af9311a32e1f946ca10
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 354p0RXr22EAK5UKwrIxyN/i1vZoESTwFGKnRRTwNA8Vyt172MvWf0gSxE/gUroctCXnt1idmQLpcGZIWy2zDA==