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
- e8d63fb953bf6688bd8bc857cd4900aa8d507072df6c5f40683e2cffe5e14658
- request
- 87dc69cd03dc286ca68203153b18b811ab923874499bd776e5a71d125d61c0fa
- transaction
- 5b1267f219faa81ba9d7c9ae4401b150b752674357ea5468a9f0b9d354b03a46computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64612
the chainentry 64612
- sealed to the entry before
- 4aafa0224f2eee2b23c191416f0ad3383db4384185ba93fe0af3ae59b6409d24
- this leaf
- b25e2ea6e761f7d1a45996c25bf05d22a9e5d9b14a714c0384c682b55d3ab5ed
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L3KI0VtzI9ZpECd0ElDCGH8+ReEstAiO13k9bMr5mMJBNrVmK7AfGYTqe6f3leLf2k/sLHT5zZhmaVb4DrxxDQ==