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
- a88aae6f43f3442082daa431b0df736c503dee780454efe513f4b45a5de1b2cd
- request
- adff6528725fef54db78d1cf723080c54df5b34461707c2896e6469c90a3e2f3
- transaction
- 13e400f09fe71277ada2ad39c5bfd28d9750a452cbc3fe43e6c35e229d381989computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64898
the chainentry 64898
- sealed to the entry before
- 400aaa2245fdc68713d3e6d9316df508147a54f16bccac5708a74f0d4f61507c
- this leaf
- 2b4769bf406d34b9c4b1ffcee7c74b7c482ba97854df486a1730a1cd28115f26
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dtZ7R5ISbXCfHGdQ7d/EnPkHVXrsCeuhGT2ChV2oaCHOz2hnRi2HhBzvnODpJgBrIJgaq25j3ugH+5NGUoxODA==