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
- 8e0074e03df6eaf943c8140b12500725e94a5ce9eb6fead55c5c8698dce0b878
- request
- 1717b84c20c3ac441374999effb262a0083b32387b1b9f6b0063f85708afefff
- transaction
- 4f09db3aac2b97b145afe2108c09af200eb4063e2fdad25ac03abe37c7d144d4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16438
the chainentry 16438
- sealed to the entry before
- b4f1cfc5b6093e7766113c3a3ed39b9f7e27e556d728f26b4f9a2be9557c5be8
- this leaf
- 3b6ff7118ed4cd522355bd6dd83bb84b46f21557bd7d9067f54397ecfc777888
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2fSfZsiPkJVuFv8CSY7aNd7+BAO5GnGK6jfn4gPfiD06X4l+V+oOECZ/L3wP6HBopxJg0mpbXDoZZSRlf61cDg==