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
- fc935a140c1e56b868ef10e17792915068d00d3927c2a56ed4129e877d81b803
- request
- f3af5cffedd1282819856b56aede79b912976ee671085c22b9830af979bbe77a
- transaction
- 7b611d567806150e9a77eb48f162f365b005c1c7c00beb4d3001a510a7e0105acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65236
the chainentry 65236
- sealed to the entry before
- 48f5347888811ad68c32319954e592f41ce8f0d8544c59cfcdeb4f1a35124335
- this leaf
- 2ce8fbb33da6387fdfcd334f0f0d26ffeefa0a124d543f84b8370419543cc496
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fT5ZXBGrbFrtGmJnKkSHsYZrOrGLVQ6dHZ6GjGdebM7XQi2ZDjlqjFBS5OmisGxTaq4nzBeGlkk9f0pjdeBLCw==