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
- cb8b78aa59c689f2419d17298e48d1fe4e17410e53a7214fb756644278abdef6
- request
- 82df38d77966e4efd07a7e8e621d03eda16e2ef6b582997ad6b5512600351691
- transaction
- f62bea2a7cb706014a14349e913c9ef25ada9106a587908f1d95f74a5fc7c7ffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21485
the chainentry 21485
- sealed to the entry before
- 3d38ccc573748efeab567df56eddaa0bb4694d8baec1a280540e029893cd692d
- this leaf
- c1ddd96c369972d4c0a0c7c42db84cffe8d9042d3f07a8853827177ed8af87f9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RoFUQWK0hJw/zNterHpt3wLQko3OSdxOjMQVpuVz7S8363XVIGd84jBb2nfKLkqT0HotpxXUJwjOEMvx8kVCAg==