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
- e6ef1a73814119e735421fb8ad49fb09c7a1f21f33664b48e192518ee21d4b00
- request
- 0921124b0705721da8af6445b12e6ccd4502ad03a9d3d20d32509c045d7064fe
- transaction
- 47ca45316e894ff5e2b200c7eb35762f0afa9eb5e2a19f36a0325114fd304eaacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13425
the chainentry 13425
- sealed to the entry before
- 4056d8af04d40becae664adfb3f44ce9b8501e52d0bdf9a7beafacb49dbd05ed
- this leaf
- ba2c1445ced6bfe47e28b40d2a7932193b41b666c029b6673eadf9acf434f312
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iBDIPBmq+HcA7yxXKHTPf/Ut1I7E7ANPkuywjKPAY06tYZA3vm/mrlWmYJujF0z2WcjNyO9Ch++Kyw9+oW/PDQ==