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
- e4d4ee70084279aea4e53cfe992f3cf981648954dcbe7a7d968f7ba6a0158f08
- request
- fc45114138307fa4b0b394a8e0fe5a1a1a1887f7de3485ff1055b5dc3d6c8409
- transaction
- a109daa3e965285c66ceae810b3ba7db43dc88140d6a4292a84b5129ad48e79dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71043
the chainentry 71043
- sealed to the entry before
- f89229f4fa5660eb33d81feac7180e780bc7c70d30fc9f71f57921f05749beb8
- this leaf
- fcb40413d8dc18cbb23e03a29e8afac326cc2743300166be97c4a2e811bea295
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZTxJAA+aWDBr11h0B7V23XC01SSsazgcKh+ohdTOL5lEmdouPt7d1KAI9voisioktRAvTeb+0t4lucuPw5r2Cw==