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
- c4483c163f78995bffbf1243cbee079aa36c83f82f97a469f234e73a0f3e7fdf
- request
- d0cb39f7efd1b01e583dcbc5168e04fb8e440662910b036ffd203cf1052803bb
- transaction
- f399e36ee1f008a288cb39d3a4823fa38633086ee201c092328a11e2205718f1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42001
the chainentry 42001
- sealed to the entry before
- 7d56769f1759089f2abd679882adfd2939bc588b16012abd0a414db59f8ef9ff
- this leaf
- 1ed78bb95494fa8cfe2426aba3949757848aaddfb1cf9295920f1e9245ca68cb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6F6uJ4Ugm7wAt5Tm7YgRklOy1v2cNdqT1I33CYNwH4cWAFBvfltmJvSx7qVT7FCJcMJ7jMz2jOtylT5HZJvhCw==