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
- 2afaa3def5e4ff798534d750b2cf12b6091663079131a3d7d1c28fefe7819157
- request
- 1f2be4309f7c51635d8ff15592f8487e7fcab27cf872155f2b21ea07123ba00b
- transaction
- d88c72e7497cc494957b79aaaab2dc57e53d5a92fdff8df9d8d3c997110ce76fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41647
the chainentry 41647
- sealed to the entry before
- bcd7ffe44cf885dcc7b4f8532ee68d5e0207113a23a5ce09ebe4274fe0b2caf5
- this leaf
- 15a5ba82b6c3a9d932a9a376c0455405dc069612ab4867955a2d58f64bebfcef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +cqmZ1h3BTKeBOm4h28JTFLfmNlxzVrKXv/8zz9Uo2J4VKBLDH7n2imPH3RKbTYcpyNyf/98qtlW4Clx4JexAg==