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
- e60b9c975d5094da54da947b4a0910891d52802cc920b2699877af750c176d64
- request
- 0555c24bc9e2bd5163ce4ba165ac869e549a93aa6f3cc917dee9d5c9efa31790
- transaction
- 40a6dc31a913967d90a8324f4fe69d6f5c6d88ccce4d01c58ffecd2a3d508d52computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16259
the chainentry 16259
- sealed to the entry before
- 40ede7b6bf50e0fbf99a582531616be9b9e4dd000e2165a4942bca3a820664c1
- this leaf
- 69aacba54ae8c586caca38caca644c2d6b465baf85ae39cbce744766661571cf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FnMYcz6bXzzbH3IJFX6CLvhnw47y2oaI1c+tC1u4PY1ybDbW/FpOos6xmo0GG4M6rwc4yMFNXSAEgTr8xizcBw==