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
- e3ca04c8d7d041d55a66d04753b7b55aa7b41c5773dfd2dad3365d57b65321b4
- request
- bfca46006be34063777c447c574ee8f4b504fdcee22fac105481b89fb5c0653c
- transaction
- 6780d512590ca4f9d196d691f820a3a1d09810ad2c96bf142b83071741ac0a58computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61679
the chainentry 61679
- sealed to the entry before
- e21b83f603c091dc69cae745712e3e0a5220d8610e4c8824a422adf5c55157f7
- this leaf
- c0235be67d7f02cd42ad8625ac6b5dccd2edf211f2544689095e3a9b3f5e7926
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JsMVLTN74Fqm//zdp/H40u1mPyTh2jxQSCLQl4qbFDsZUEYK+MHveYrwLIHbU3PqKC/nie242UcWgeRcZeYzAA==