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
- 85ff74e40b0a63a064835cf7e77617ca445a7725003b50251d1aaa6ca1fec7f1
- request
- fcccd43b984de1bd93d95ee7a26765ce6f7ef1a280a23b5502060541716b3bb9
- transaction
- 9bc5de2d0da218c6f9384bd82d512cd3d8620f353c13161f23f79a91db22b879computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27466
the chainentry 27466
- sealed to the entry before
- 158b6c2920a7b2d242a28cbde375f13f285612bd3d15436209490058abfa78b1
- this leaf
- 522a7342b228dd13cf8fd7e95df392d6052e353da39e94d0311ab80d87cb75d7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eURA4hcMbf7RLe5zZuMe7UZcolULCgg7YS65rkks+8pu7W1hkEN2bdgi0uyKIHIihWtULfNArhUclzP7kgSGBg==