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
- d77f9c83616423a27571c2ca0d808dcfcadb2b8b67b8241962f0a30976c7a189
- request
- 41251b402e23c0bdbb8d8ae00514eb9fc5ead93c690a68dcc4a95748317e0a42
- transaction
- eae2e1696305bb70877a2091c5c02c26dbd730bdee56cafe06e5e8921f13b53acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63428
the chainentry 63428
- sealed to the entry before
- 74f5f8992c6c42c4e0d00d72e4e73dcfbcec48e7d965b60e2cfa05893fcf9224
- this leaf
- f6c5e54539089b8e557b8ca7c445090f65af840b117da086a6f01b5097c0a7a2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 87NbSKVhlP+Yr5JQ5xb8OC9j3bcUuSBa7mWGqpGirD88SSAXZr3DVSRoYIy+BcH9xpZV8d8wkck3IjA2UWdvDw==