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
- fb75b26eb88b5c5047c57d58c2e8d5c3afa3d0fdba5296d81aae05aacd722684
- request
- 99d966635470af9066135d2ac12b925e94f0e28a247baabff48aa8919733b0cb
- transaction
- f3152f3d5c133db74cc9769b98d5f6c6cea8027aaef43f552b887e76ad22ffa3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49636
the chainentry 49636
- sealed to the entry before
- 7e5424bec03c24e26bb82b95ac7ef8a12192aad83f4298b73e905b22971a7444
- this leaf
- 8c89f2545027b028d6c5def0bde568291ee63bbe3ad12126985c4cdff6b60e50
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PbEiTEFG5IXC5RF/89kSnKBeXCNhqJsbbxOi7i32nhnHpHDOVkdHD8dQZaD6XI5aG6EdYI/ORc9XYA24YsX+Dg==