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
- da0297823be08df5e26746fbf940ebae1dec7ae8a1484f8ecb39eb3a95de950b
- request
- b796b9234f83a14bf1c9f3300fca8bc81d15fd1ac9e1717e07cd1cb88e44c145
- transaction
- 82b82709f8b489adf3cf7716c378286a5e1dc2a2eeacab4bde60746efca23aefcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9441
the chainentry 9441
- sealed to the entry before
- e66da1b8ebbbab6a7a840951d45e8a90961146cfca5f0fdf03086a65affb9224
- this leaf
- a239d7011cabb9e799e0c8a919c95103376e038c8b1b86aa15c3fbb1eefe7d78
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- l2nC2Yp0+memM4ghj95Qr0TTYckF3vbqKf2gBWAOaVSBGm/I6t2k7tLRnbRzpx+k9VwkYzktNzfQwuDEdOvoAA==