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
- 7f83c24839cd1204ee68dfa45babbe67b3c35d7ffb9ddbefcb900fa75ef47a58
- request
- 16c2ba20a7d11aba1c15f31fa5d128ae179f98c3378704086696fab5848951a1
- transaction
- 7087275054ec681132173ab7ad0827ea8135f40e89dc6c6fd250b6da0349b088computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16556
the chainentry 16556
- sealed to the entry before
- 61f424084209b6968a032b669a841718d399576a06656b9beedeeace82e9f105
- this leaf
- 24c977c655141c8e733949f2ead9b6c440566216015bb4fd5e2b102a47ac2ea0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Qr4DuZB8VCN01kwQrfpr5UehabZHJp1HZX2xoUnicQwK8HiT8+mkzEbo3cgceORscEgcDwedPJ/8Yslq6Lt7CQ==