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
- 376dda9aa84d8668087287d4a4778b5ad23ba77335721dcf7331adebb53e172e
- request
- ad41fcb87accff5be719d4e23ce25b002ba48ce20778eaae02afa16567c2ae51
- transaction
- 85b1ea6e68daff6954948e0e5fbdb401d6194c82f886a7626fac02ea2f9adb90computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46525
the chainentry 46525
- sealed to the entry before
- 35d998136e598e7df703d7b0970dedcb654ef08710f7e539254f5c9b7b044bac
- this leaf
- ce2a4eeb0113bc1f26181e0cf921b57a08d0c31733900975e27f30a58cc5b65a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /Mn79iH35aIvUa6Um1d2CWhJ9BDKqKdRyttBBVmlPWU2KCFvgj3EOOnF0ugJMrvtd26CvLBlRfzPRlpFxCVaBA==