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
- 34d35433443ec8bf1ba700c72de7730eb632911311f01e686400c04420fa1547
- request
- 76982a35b8b15309596d8f03ca21d1f48ee7510c1e102c916246d89e267490c0
- transaction
- fbb08b38a0329e687e5f64a31863eaf64a707cc9ebc0f7db8b7979c643be0cfdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32806
the chainentry 32806
- sealed to the entry before
- 48da6a1522635e6cf7e40f363b011558615cdbb39b13bfb6a1a702ef9739e08b
- this leaf
- a2b584899cb9898dc2d402904f58a004e2958cf7d83c24d654f6552d1b9802df
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TFjale0ElIpIoNE9CuSt7b7AGMHj0l4vUolx3tb26jqWvqgc7IjX8ud3os/aYr/7TJjaOQN1jhxW+7y2H9dXCg==