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
- 4580d97bd34425be4e3c6f7a0f96ad3999a88f5529a8a886880f770055626d16
- request
- 5ed5ac5f2a90c19034114fe55c40a2aade64738cc82b932bba256add24fb67be
- transaction
- e2147ef5809049dd390e3b455d6b4fa5da69372339cffe136d03f90cc82c8e13computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43702
the chainentry 43702
- sealed to the entry before
- aa566f66304277d5b67875638c3494d310788fc02ae8fef5feb0453083d530aa
- this leaf
- 3af964d4a1ed34c0a3dffdb6dd2013bd8a2bccb268b32cab6cec7da46e1ee869
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CxQhwiwcGrlYRzS/wcv5uAGT0+zTVoin4VDs0q+7Etsup3zw/ZWEfCwGIcScauuu6yDf8BIaLtU6BKxXU1VaAw==