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
- 0b6d3397d63c1d1ba58956066df2a69e42146d47abb4ff444ce6661f3e08b599
- request
- 53c0f84606b90d4770a39d9917091c01ad9694227ab104d1369ae51bd01c6f4c
- transaction
- 6ff4b7b9c4ff2caa6b6807402fd7514b81e86bd12869348347a9dd6b3295ce16computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58790
the chainentry 58790
- sealed to the entry before
- ff9745db3d1b9d531b67ed156e9a8902139fb1ba7318d7d8a43b7e9670d241cf
- this leaf
- 3478787245f80f5669ce82ae5738d9b1c10ff1d45b9933730e5d35ad72894012
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- prPmLKfCpc9NUUepwnYTCh3uUrVJOs9G3eXqy+OCXZ9ESFkXpMY3sDmg1HhvX3efa6fjdy2tpJBNabZee5WjDw==