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
- 78636cc398274ac7eb65665305f22439c10078593ef4e96c74f7f5a7f339ad09
- request
- e4f81fbf3a5f80f4563bbecf302d24f2c3b4c3a8ad447ca0c776d3a88cd0d0a6
- transaction
- 2535cd6298740952ba93c16b808a47768ddd1bf9d5beb5ebdf970a5536e070dacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34345
the chainentry 34345
- sealed to the entry before
- 8dd595bf9af80f4c708dd7655f293f08eeed98e54e2f832f513be775bc4a6ad2
- this leaf
- b052a94ab48a4a54b4c7c426226d6864b55dff3d3a81694b5a9f16dda06efeb5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zJrhtfMiVSPGY9oE4OH7f0U58HGkErpZUfA9GEs/yDxG4Yaq6gkmas8B01xp1PA2erxNV6ZSg9qaWO5JqT5sAA==