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
- 9dce40afde70873b28eb4f70283359563bd8cd533ea7a795a2e55090796d12d2
- request
- ffc5b45967d90cda7cd75f68d9a3d13cf2034c814d4ecf4fac11109fccb37e07
- transaction
- 8c53ca160805a4c85c35273119362b746e871e39289f92f991c4ccda22c88c12computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2480
the chainentry 2480
- sealed to the entry before
- bb3db0abdafb6242a0802b83987f9302ebfcb347c6bf70fb8bb74b7f66b5fc81
- this leaf
- f3163a3247e26c5232e19ecda00f5e0dc97b4bcd9a72acd2b76d131f9b6bc323
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +672GbjHLU2AQZomxrCr0vEzjhjcut4gsaJVnEYU8r+tX6SrJjSah8J7IgWlD82ICuoPGQqHkmIIjpz7zEavDA==