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
- 01f6cf65053a8e3b9af333d5ef9522205cd9d9eadbe83b6f52556522e67aed79
- request
- 79c08fbb0bf2b35b27d0e2889c737926c423f58575344dda1f246eb1fee1ebe9
- transaction
- ec286cbfcb58b185660cf7a8efc8e77ceef161a0995a2f77662b74aceb89275acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25277
the chainentry 25277
- sealed to the entry before
- aa26dbfbb1b35b4b1a117ebdf45ba68cece093e7939b089bd587dd96b571ad54
- this leaf
- 9aa17014e188e4f6795e5e11c686a0293184ad56c85c091256a6bb39237fa9c4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YuD7+wJoXxJ4utlBS0YDxLlGf37AU693XPJ4t11O4RCeHvSa8XkZ16PY4kOrJQLNkH4vQ9IOVBqTWZE38kZiDw==