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
- 5e2a8a32b0da63fdcbff0725ef8726ab80703b7891c42121ee6bb571ab564c82
- request
- 5380253327db8ede9177c813301a4cda8edfcb5c57149a366785915830f1cbf5
- transaction
- 5818d3d2a9bedcf0d7e66f5e0e4c6cf10313eb60d909ce61605d7acd57c8257ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69924
the chainentry 69924
- sealed to the entry before
- f52abdd2ed428c562bd72e6e4d037ee4dec019db36befce175dfe13ed5f7cb19
- this leaf
- c9861bde92af20511fd77b9d2ea21381c8b6e6e782dc8dfa4e36474a5785a5e8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pBS0eKmFajxQIAS826LmViA7EtQmmkXz9CyceJ4sld8Z7T1oSf5CO8lG4f9iU06v7yevDpvgpAe4Viq0gc1ECA==