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
- b41607aca8ed988f29a53dd79d31d5205ac16f4cb015437759d900314e6e0902
- request
- 30a5b2399535f5bc3d92992c50ebaac4bbbda33896cd26654d28afc1abdd3c70
- transaction
- bccef55e66d2bc0a42b3b3b948c597333aa79d982e3d0476a9f97a836723ee6acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73098
the chainentry 73098
- sealed to the entry before
- 2264b5dd76f80d806bfcbc142f1cb09a79927c626b64a6f09544f7ce20d2153e
- this leaf
- b70dff375d92caa044c202c36576d4833acb2f8f1befa5ee79ffd81794b62f13
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 34SHtCWAHWXKg6BZvOwlzFqJi8vIIKoGsBipWOcw3gy/FatooUxg9mIT4VaYblVBPOWBxDt5llCu9E6ecxD7Dg==