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
- 2ba2587ddd4a96ac30b4b9d5975e7cd232ad3547b8427f638d443f7810e06d56
- request
- 8ab1306b2e00491a1f061a323ba1f9f4345dd0fadab8f5b4137d16c9a9a463ab
- transaction
- fb8770c913d667e0958c4c5543584f0f8b03dd15dc315c58661911fab6256854computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20436
the chainentry 20436
- sealed to the entry before
- eb4751b9513f6866d665d4275b4028bd7849bb39e1cf6d1710649bc3ee78734c
- this leaf
- a6466a2314f3b1804ac1fe4d0b8f42b22f4714317afd9e069e64fcb6427272c6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ry6dO++3W7Esbr8+vHWMVe3iZQ8eUFNOnpl+gqyl7Wi/KGlANgCmusAQLEgLTXl9VgY2PVvk/QQ8Rx8dT5CxDw==