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
- 28ca80613aea7fbdee45efcc799adc0cd9a736ab8e99776ba37b820da0ca323f
- request
- 8ad49432e0463158635187dd6d97ef3ceece8509479c66892fac79a86206dde3
- transaction
- 2ecd09378e73161a8ad51afb9eac2af51b18a82a65bc9e6096a42086e0cfee76computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20400
the chainentry 20400
- sealed to the entry before
- 197c5798439c77dcd8b4fbc7faba02388f0c415b62eb5724db0efe7d70278583
- this leaf
- 17a9ac61b7e6a3a3adbe3336bc6bf83c59ff1634e570a5562f18ee599f7ba3ec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PwgaLJNVniXPerma7j9ts/coO6DEwitARmYF4heCt+LIK68mQHJh18hNmcqI7wh1yoHLmZVPukxQMaLkwjPeCg==