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
- 34cde8b3cdf9d100c59133af3bdf4fb184ceb45ec8722d4392898179f440d43e
- request
- c1c0cb68e385a1487dfc43323576a55c17bb54868555e5ff63221726e2a9fd60
- transaction
- e63f3036e4c4f7075eca011fd7bbb584ddee13992fffb96befe5acba54ea53c7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23384
the chainentry 23384
- sealed to the entry before
- dfcec01bfa4f810e724c69b69b29f8017e94989e0941f9639d329920f937159e
- this leaf
- 7e5339bc7f0893cfd604cb5f8f492d3fe014e085a1753b50b479d290992900b9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- r49VLDduneEuabMW9svgd+JacGu6FzYMpX8gARlZLp1jbk4KM0rK4aK3Fa8JYoZ4JQ1zXzYv03xtpfvkKZHgAA==