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
- 4543b55848742d5d3c59a01c9a28253f80e3c724a70b8f7cd3526be80881e20e
- request
- ca3eb6e10cc8cf27c02c7234d762e88af9428385560bc216741fa2b6450bb7e8
- transaction
- 928c93218695f9f801f6b9b2c01387cbd4f7d257bdb063bb805e82705650d498computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1260
the chainentry 1260
- sealed to the entry before
- e425670ea379474ac6ee7adf5366746709b308670da5311f050229f861b169f0
- this leaf
- 10fd48ff1b201b107bc2b9d33b6646a305aee12cf9bc2ff435aa4ae04ce7068a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EUM1nfJPki5ofzQoOrgljxGl9OF3HxOxMkI3P5i2wxIf+S8OZIIqDtmeOAPny0ncA6EC7f7J9Q2VXvhrsicqAw==