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
- fa90b2f46df5feaa0b13d5e2dd3a898bbdb61ef2fd6126902a83d3a44eaca1c0
- request
- 93ffc36f80c77fb91404ad029f84fa97743ee43f8956b1ff9969eff0081575f5
- transaction
- ca33e59fa2380dca41db5d50ca1a3580abb842c3eef7966b51512296690582d7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62067
the chainentry 62067
- sealed to the entry before
- da7b769bf0f6dcef6b7a48f1b7b031763aca089243cc679856a960e8692e96dd
- this leaf
- 05512f82a847dd4dd0d892bc79df6b4f5d476048ecd1121d2e656102accfe917
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 50cSiuNSlVFLxIq8b8Cww88GJWr09cZujdDwCR674p1CYZpScsmlSUTvcQ+LrfSlIJPUOxm6xz3qzqX7UX8mDg==