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
- a3cce3a44c2f6572e63a796bc9b6dee596470116386e46fa30d1629e5a7505db
- request
- a084f74780b6df7d16f0502da60ebcf64bb98cef75ce29a7bc0b109246aec353
- transaction
- 012a47de77caf231a0ed27488e03180e468ef57670d4d42ce25ddf1bc1d91992computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2125
the chainentry 2125
- sealed to the entry before
- 20359aee59039ac679cd58ecce6b055cb4bffcb63e1e6670c8e7d701cacad54f
- this leaf
- 12298bd79067e4e9562cd35a0c492354c3a499d01609aa01f6b27111a35a8039
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ojs0sb1quixW0QDOsSbHIaEafh/lJF9SnFLmPl7aDhRtQXec6XKjUBQPKpmUfXaoHVfotZTI5sdDd1EHe+MdCQ==