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
- 64103cda52faf105421ea0ee24e389e8ab5abcd2885d3485f5bc04abc7407eb8
- request
- a676cd79d2b4b760b1dacc50ce6876311d84f248ec90a401c58443aa44b49102
- transaction
- dd966330bb705fde9c87dafb5c2009c20e53cc1bc80573c581e8fdd5bb17a8cfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67143
the chainentry 67143
- sealed to the entry before
- e1c22c5fd8b5e12f777c65b65d1c402bdacec08e9c97f876debe93938545c7f6
- this leaf
- f88c7086137e528d29454c4681b3d3466791d04fc36cad220e66eae9c28672a1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jZU5ku3WiIh4ubTlAE5A81iLB1mr9E6M01uSOiIBCtVoV15AG1q3KhoumEkTCkvA1YJ00YOoGi2B8WxlfuALDQ==