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
- a5e0ff116689a90982ab79d053fc5e2793111524f5a72a2d8b2bf76a836cbbc8
- request
- 79cfd415ae711481b4f246e3ad64ac8e66ad328ed0c5b3a817de46cba5390a8f
- transaction
- e560adb3fa3064461f051881bc2ff367b1d8b029a7c2b22b3cd408e3a648bd41computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32693
the chainentry 32693
- sealed to the entry before
- 54f4fb3031a523fe5d913b1b688c9556941ca363b1d7e71bcce6f7d9b4bb8330
- this leaf
- da7ec65d7f03343fc0e4a198605509191dce0a65572cf288753c3d3a222a1df8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lzs6K1Ne7l4znG2VAY8ex/ugoFCvD4ueYkVxTEOama8lgKglayn+T90bQnSiem9VOGMvao/8J2YbPT9iwPbyBg==