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
- b24c4362450dab67d539907e928dab8465b4b2a77e390674fa6f727c37d84407
- request
- ffe4b9695f05ebdfecda7238d5e4d6cf0ce85ebf4e86d57aa25dbbae59517960
- transaction
- ee23b846e356f26e139e63cd245fb96c84376402274385de69b8135499264fd2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50627
the chainentry 50627
- sealed to the entry before
- a64e9576e74de9042b52e2eac0b2a51b11433e6d747f542f9db4fbfd3b3878fd
- this leaf
- bca0d2c80ef3cd5f06e70c27a60d09989506dcc052b6af2f9facaec7e9c0543a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dsoAdAdHP7Yw572Bv3XjfUQScxaz9zXppJti3ki0rTM+Kyz3n+FMdQgcbuzm5CmzPinY0Aa19gxBV4CBw2isCA==