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
- 1f31f9f49607ba8d7fd559507f401874dd9746291d8a8d51162818b222ece75e
- request
- 9f6a415cc663e3a453c10eb68561ea4ef2cc7c3e398b0f0ce4e64daa07abec54
- transaction
- 8b26fa2d4491d10d91916a95884768a47c607676ac2007be49d2e5aa2456ef41computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63762
the chainentry 63762
- sealed to the entry before
- 2fe16187b4f224ac4937295ea6f0cfd764d7ceba4b8f30d86821e11812f67322
- this leaf
- 46874f77a42666e197e87a4985410ae51804a8fc1ff71d374a06fc5bdab7cdc3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mK/ggBWEeocenxxxRWS/hxqLvgHnAz0alEtQS5DAfEDWzVf+TmdNIhcfr3NTJuT09giHcJLj9KAlGrLtWYLFAA==