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
- fc450e7816c3a74483ad62f3f7db94628eaf0d6446ae42e17b98e3b705ac0ef6
- request
- e21538dca8c02411bdb83a6433fb185feae3a333113dbf3980b8ff7efdda8315
- transaction
- 261222cb95fd0dbbd7be405a91e870752b216446cc898fe7047d6ef04402486dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31914
the chainentry 31914
- sealed to the entry before
- 1f406c03e7fc4880fff83bc659f21100211c35ee0656f3c47e1ce24dde3f1806
- this leaf
- 4c5b2adb271ea3496d6cdb7d7344fa1b64cc365b081c17d0c14ba442bb6f8fb4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hHCkLzLz1XceZPi4ZGDklUaUELEyIw+1um8bP+CxE6rL3Q9qZD+hPqK8hLziOHCJhrO0oIrcSjgmRzdNB0DsDQ==