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
- 66a39f0b640a46e8336a86d35eb5818b33268f1f00ec951b68ffb1e90bba040e
- request
- 2333fe231364b90b77cb21d3951064cac0f9bbbc02b4b86894ea24a711a082fe
- transaction
- ba72bcf2fb51ada5ab78b90c09a0b202a23514d0dc25f27c91f416f98f4a14adcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70578
the chainentry 70578
- sealed to the entry before
- 09e74c13056905138220cb65d1c863b8aa94f57837b23be3a0c565c33d22bc99
- this leaf
- e4f7dfcc2580ab01beb11feb3b168bf36911fe95ed726ebe068fbd8c25892784
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XiqCCxuofK8B+76BBi/KGw46nfiAgNGj+onJta5c/OV9Dt//RHBvHHJStNh3YJFpI5gUwye8L56Gc+jZkWhnCA==