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
- b09157bcece33e26ccafa70519a3756b7aef3a5a2f7537cef083faa7ade61fb7
- request
- dfe659e375b0efe867811f1e5ce86355ac42f0f1248fd3cb5c659959e2b1f613
- transaction
- 251c33c678e17cf52ba9ff9d2eccfbab93e90853db9cab50b08b6c7f9622cfc3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21541
the chainentry 21541
- sealed to the entry before
- 4a0414e0378c0f1bdc02967c3da42d287239f4b529dac39a4714be2ff6f482b3
- this leaf
- db835c8e2d54afb2f3d2582b79bc4677a6bc9f66f16bb99a0c16b43542d8b8b4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TjT7k0qf6BIJSjljuCTT5ZzEFjh+V5KdD8qeq1ypfRWgU4mNk4L/CfmZ3WiEAa+MmCOSfpAqtZZEANXQN8RADw==