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
- 49d76e550a179f0536e5d4fb3da065eb776133ecfc2d9e7c1c1011003ef59787
- request
- ec8a2d22762b790d968abbd14638c22ce0ebf0fc53826125f9a5c4a289905297
- transaction
- d26881aaf960486496827fff09f443ba6d96338a105b44ccb2bb27ae64ce06fdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4266
the chainentry 4266
- sealed to the entry before
- 49fbcc01a0fd9857f8906affc350105faa7fd53adb80ffc1675a83d691e4483d
- this leaf
- e8e13002141d68c0db56a1249eaf2f81c22ab22ea31653543c24dc65bbdc87e1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AXAM0hfDg4LJ6INYZ2pKa2vF5sa/x7fErzd0n7XUMoAMPibsQol0IT7jfSsflLQ04kbzB2VmKzlvLkN/zSp2Cg==