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
- a1dfa5cfa41f32db63e52c74ef990b9e95f9d23b82e6256fb69e87c7a44dca78
- request
- 52348f9595862b52788348462b5b519b9c543b6ea0c49d5a7765ca7f8b33d8a6
- transaction
- 7d5ca4e8f6633e698ca0aa3356a98938ef08b1454c3e520d4dcfa5bc846885bdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8022
the chainentry 8022
- sealed to the entry before
- 96325bdc603a905bece21bdc7bd80e280469d0989cc21e35a34e4b2c0e8de293
- this leaf
- 255265f80b6677870ce088f6aa83ffc9c8f2db11fbb41b1f35827ebeadfa0011
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3aifM+W2kOauKxsSagW8uH9ElzKtTosvGOgO3L+fl2F9uUmzyETG6N2XDtx+oM+syu/5bbCJoMxOUZkceuj5Aw==