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
- cbf60ecbb4e7941d9b0cd572cefa9130b8effc41aaaa5798140cd1b5aabb9a18
- request
- f1a63294448939187cdd687479c45cb38d0c3727595dae809e971df3f4f05d15
- transaction
- 79d80a95bed37f6204ddcc174d7a4d41c99cc790a18726795c3f424030da395bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9169
the chainentry 9169
- sealed to the entry before
- e8514602a024b74cf8f755f343118c0e7920538c3058627a39efe98405de9cd5
- this leaf
- 61395a2c455f4f698aa748b10992cfcc425c895c8c567b4759b154ba5e038c8a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3A5g53B7xyiaMerKmRBqtv4q2EO4eOeuVE/+YUiZpYl941EUqiZ7AGCrlIK7vXQjQVZDce08XM730lvOcg9GBA==