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
- 39e7f57229be4c68e863ecd57b08525a0a50cb404696782d67134780e6bcc010
- request
- 6a43b5d2ae0c8783f0b65144970097ab84c49a21fb117961cc80292445e96eed
- transaction
- 5541c52ebad3ca03f9df83e2cf670a9a57f07674296f7009eeef2b25d00e032fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62772
the chainentry 62772
- sealed to the entry before
- faa46e86283ef7bafe70bf3e0c556f2813b636365d6c7add3e19f6a117c6ecbc
- this leaf
- f9a83377635090d5ad410c6c5d08b58b2053616b7c686af56d9fe7a514322eed
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- p/pzldfFKSYY7A8mGq//7yI0kOI/Zw4P8FRUjgdJMHHQz3Shbm1ohxsfqI3LQEyXFvYcuNjr0bH/pWE7DxEADQ==