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
- 01ff9c6f37477293c697b20a2da91430016151aaab077a73213238850b697403
- request
- 03b38f744e305381665c339c5150973e2df1c341c25718dceffcc10fcf390e01
- transaction
- d8f4c74b36bba9b3a7f15d347d1affe220e874a089a8223956d41d9cdefeb4b9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41947
the chainentry 41947
- sealed to the entry before
- 1a6b26e883ddf77c7e2039e34bb769f79b5ff5cd3132ada368f93a267156d496
- this leaf
- 638a124641362fff0da643d6783b3b34ee52938753b23b6ee710accad08271c7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5QZJS30yaA+GtdHsvOrmZeasqbBhEyZrMzf3Jz4yNSAgCITP+/6GGjyEaZsviO9euBLMA+fBoLYQmEFS0mE4DQ==