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
- b94fdbf180047dc97ecd82670308bcaf59dd8b5dd66c09eac419cfc5b8bf5944
- request
- beaa2a604e1f74f4b4daec41481fd63bb29b6826b3dc23fc80a799c29d63c149
- transaction
- 57af6e7e2aca5c10ed0a8900bc2993f2ed92d7bf609470c037ac49ed84a4ea28computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60256
the chainentry 60256
- sealed to the entry before
- 0cb8f5402490e375995762f67f3303d6f2b922dac43352a7d32fe4846d033079
- this leaf
- 29e8e9432c15b30de5286e470fcc141e0d8614cf1a463bf3634c1856b2b3aaf0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- An5Sax5rCBW0RluiRHfuaAcmeHaaqxMf8jXAhU+cLWA51QFXu2j4KP8gM/lLXYtnXRXXyfKGebcajcmYUy3FDA==