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
- d9695f35b730749622b3926672450b3cbb31079f4999638f3bc1d78dd40d6e76
- request
- b7195e7a98ea8763d20e64a189e2552c753316be1854ae6ebd3e43ea957d3147
- transaction
- b36ee61d5aa6614b6805a8a353d985b03b5bbfe1461270954ec8c9d4142b1b68computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72598
the chainentry 72598
- sealed to the entry before
- 6b1151ba4fc9f756491a64749fcb426d0df3c79af921d09e5113c6ea555b622a
- this leaf
- 7526e01eeeb0eea0277db5e8df7010385751e5395c916946a60a848a570fa035
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gFsrADwbbey4Pgl4N4uZcclHQJ2780dZrRt5pVf58YHx/IlAujcCLTO6D/w3IxitRMwUn0DfxvjJJUjMOTY1Bg==