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
- f3fda9d35072f2eee20bdb2152bc6f61cc8807a5c3a390d66ef70783f70fc779
- request
- 8fd3f415a26f92bfece0eebbc1edca18fa1ec363607822de92f780760eb3d54f
- transaction
- 53d5e0dfab97125d63db7f5a3db8d486485f73d87209fff4fc0c679432ec3122computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57662
the chainentry 57662
- sealed to the entry before
- 90204973fec58a73b98019b498e45d6c58440e2629531fa9beeb6aaaabe5e52e
- this leaf
- e56b781e99721f18cca72e92dd04e8b87d1f62e36056618c5e474ec9714a3269
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1A4kaHjh8kXRVch//vS/6BjOaJmXxz3MJJfmbfUvmLjgsJAldLIBZpszKQqmfyvO9f9UY78fPIKwDtezKyhJAA==