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
- e9b31c146ca1c98fd24658220417fa6848c2f6369a0c182c20dbe6511224884c
- request
- 2778f33a97e55824a8b7a50f98e4a85b8d5880d225545f025163071c73bc6fec
- transaction
- d537754f69db49186298454c3c16c41656c1029bb5f556679bf548018ad1f49ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47562
the chainentry 47562
- sealed to the entry before
- 4ca676e7b129f5818843ea04596bb04594725bf1e9208dfe90ffe4dc07391c2a
- this leaf
- 4144d7a60f73e956dedb8aca8f3c59a3aeac73f2fc5c5a0c44fa0f96615a6f75
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ihzMzVuMvW/9C4pciMMdOHZ9qAEAscEGJgxn5ptymJu86CRdko45ixTNs9pGnr4SqTW7qd6tfOTqyDG/kqpICg==