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
- 7dd7c1b9e1b406aac1d27d09e8b37efd1cfb796a3c1c9b42ad234c4950c05604
- request
- fe322698592d4c39dc1be5dd0184194e54a7ed55241919c16a401b62a6768912
- transaction
- 94f76ab900fbb70dde2414009cf8cdd55f68bce2305d9b6d235812c5356c0bc8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23194
the chainentry 23194
- sealed to the entry before
- ec4cd8966d18e19a722a6d863bf4d02fbfe6e1cab8b3f93955c43de4a89ba488
- this leaf
- d646c6cfafece66d53ec7939d90747538dee5fac13a62916fa558be746b7fd92
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K1dVFECzRrKc0hQB+CtAxlexL8tNNvWnEGuPa5ypmga/M388XGInHn6oB0V7ZLtIwlJbyciRUPWvHGbU5GttDw==