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
- 783ea809aed8f17fe71ce7c7410fdaaadd54dde4e4defa17f07cbfd7cd66d2ce
- request
- a8862502b1f5cbfbb6fd5aa16952ee3b42f16efb3113f3dde6060dad66d1ed0c
- transaction
- efc2011b460ad1feddc32716e22203373ef4e2e53caa1d2ccac7ec66694486fecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 571
the chainentry 571
- sealed to the entry before
- f2369e58ee5589bd7f1f3a6c72750fe7fcb004c3b7b9de89d0b2fdf77b234904
- this leaf
- 84b246f420c2a2916c35c43bc7a9e9c173087615b1dc19ce399e8da3e4b58a28
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pdgD035sT7OUVj9i60axMTzSV+t+lrh25OnoKJEIuCi8LuOT7EThItGsArKafBpN150AUy2P3klrZpWmYt+hCg==