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
- 5333a90c8ab19c27a662ad17e3987f91ba6935f5e6622c926929e5e9347182c8
- request
- c05e664b2e2e7f49b91c42179876278f9b5201977fba36cf91e17f0a9d96baf4
- transaction
- 42a6a52b9479249084645c44b2ca41592abe637ed7bd9c14bece0eb32b96e0c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12727
the chainentry 12727
- sealed to the entry before
- 048d1f1c6de3b8c821223944cac60f43d03686e032570edff9a9049e6f2ea305
- this leaf
- e9dd530e83240ed57bbefbd626e0b4f2b6e1b4cc6012efa2ea0bbe5fdd425da9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Navx+rvD6prUbvRa8RZscqeqwlaEj5Hpty1g/iM6fR3RUOZFJEEC+6SkFz+oWoiQ6VAWalUguRoKIyWqi44BCA==