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
- 6aafd9cf7c8de91fc53d1945e40f96a944514dd304254ac438384bf89147cd75
- request
- 0a86eb4977a90f9daed155a4a18f565a3fc82910d4b9a172ed09479f4844ec1a
- transaction
- 9b832a43339c49a89c566368751cea23a9429e9c554b1caf28017ac55ad76b01computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7259
the chainentry 7259
- sealed to the entry before
- 784ca63ff50ac3e14101107108d3e67bd5af563a26920c2b1ae0f65b8205c3d3
- this leaf
- 49e17438e3e8efa5ffe1166ecc1d87a748d30b6fb670d7366bb8e387b0665332
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Qko0yhKVrLjFRIDRNEZw9Ex+GDSdQ7Y3qC8yqG0qn8zO4Mf9A45FUsKgGlmWmbe8q+GC469jKiZe9tVEXK0RAw==