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
- bc4347ab48a1d9830f76e84e67c76bb3205b4df943881126d6944211097acd2b
- request
- 769b0c48eb391e4b0d3562fcb0c50e4aeb3a4ebbe5419358d1c64ec0e1266f0a
- transaction
- bd433e202866f40942ec714fb2ea6563b035498ee4eed230124c224af8f23dfbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76234
the chainentry 76234
- sealed to the entry before
- 3dda5e759b6c8b034f4a7cacda7a9f226d3da71bc896e564fc4cc19b663416eb
- this leaf
- 30e959b759698c9c2c6b521d5e50d925cdead5ac11dd98c825bfedcd6f57b59b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3Jgr7wuoOGWTNQpN8POWII5z6u7V74VV4Q7CxAdVPYSS4VlNUqZ1vnS/DwOQlT6b1ZVvpMGbhXfB+8kZcI1xBg==