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
- 8dfa1948b8442bc6ec03faaa178f1c336918ef5c4bc2ada61456f72664abf2b9
- request
- f134f8923c64f60b5299dac225de3fe9fb833fab0e344da3c30b1f493c9daef8
- transaction
- 1d49832e5a604da8efcbd6b48880bef5d0a6bd2f77e9c18704435816da510750computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71030
the chainentry 71030
- sealed to the entry before
- 6b6452a0864cd080135254c1d8b0a4f63332a36ad6800440ac66821c25be67d9
- this leaf
- 14285a0ce23e371e8540ec9e1f6d42aa65637300cac6d4933ccd571d54036f01
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dBukfQ2WmG+HrKf/qhJ2jOZFzdxwS6Cu45fD4bvAWViJBHNMfAJ0eVlGapSeEp1lJr763WC4jXnvrJafp4+wDA==