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
- bb79bbbbadb6627a0ca9fd9e050cf8da84a5fb1b8fdd5558dbe85400bda0d90d
- request
- 54c79e2257a62f1adfaa2170fc6a3f4398748120212e8b8d0310b38fb45b1df5
- transaction
- 8e3f3cad223a3bf7943e5505e5638590247432da815f66a6183e54ae860fb0cccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35800
the chainentry 35800
- sealed to the entry before
- f5a670414f766887d149e97fb2f00d9a5f0c3f29bdee72531fdf17149b96f0cf
- this leaf
- ae8c748a51753bd52dc29b1b9b374c56fe3a0f3fc0a37f4111fea2d807734ee0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- l2QQM+i3StDN/ns4GyXmzkEz6hOg7mFg7G3BHJqx1ZErNZjzYRFpNZQ12K4O/qjMDCgYaUmknRRlm1uzY1J0CQ==