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
- 6005f6cdcdabd33b55487e9a1322b6f732c614afe81fc5949eb1be0eb5cfa2fd
- request
- c6e7f324cb2241749b5ca7099397eafa128ffb062ef9a0e4488f1b6dc6650f64
- transaction
- 08b64592642b25c83996c88e255626509a8b170196915cf3c734789d2e641938computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64968
the chainentry 64968
- sealed to the entry before
- 38dbfff62d12ff6f60cf97ee7004bf2ff81cb0c14f66defd1e089cd5c61c3b3e
- this leaf
- 32cd2853f7579f6ae44bced7fbff91a3d41e9d241b9d19f36e28bf2dd11d851a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uxGjEFNrD2EdFe/OgtkZN5M9iZd1M8GailrmgAivJ1sehzl/7jmeTWJM8KNOst6noUp8at29vP5nyyi8cJ35DA==