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
- d78767a95e0293af96407cf705f91fda79bd5869a931ea0b5805b165ac66425e
- request
- 5177b0e5d669d439555b4ace5c8624af3b776dabf21440268b580bffea5ffc46
- transaction
- 7e1dfa86059f0278ffec92aff8b63ebbed100f353a1ebd2dfc69841aa110001bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30636
the chainentry 30636
- sealed to the entry before
- 70bc14acd95156005d0f2ad60dc0a2ba172e2beeb27c3888c8c4a257150b259e
- this leaf
- d20ffccea35834bed281058c26e10179b8b26f98b1a44ff21bcc904380be9f5c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GCOyPjEYi3dEGQ1wLgrfq9Q4kkzZmcnv8nxGp8qxqpHjgC9MaRSf2f7zv77yKsCTJoQF3cMUAwf+EUi/Vi1uAQ==