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
- afd9b85db2af866034c58d45e498d94f8c1015744892c33fd5d7e97c85b198ae
- request
- a43dc54b1655e2978e7910f66caa21a9b4c041658e8ec77413699788200c0642
- transaction
- d8e9c0d81eb1785823334dc1003ae56137b616b6dbd04503130ec370d7935965computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26533
the chainentry 26533
- sealed to the entry before
- 25b84ae250bc7e59d2c5b7ca0ab7af46684e87aa016e7b3e2f9091b53fde4ca6
- this leaf
- 8818131a00d7c2d3993a477af9735a2e1931c940eca96e1364628cc4b80066b9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ht7HkXT1zvzI1j0i8mwt5hxYlf76H3sWBRlDbf7JTj1kXbsol5RWf2MFh9gzfUiQGLu1oqeSr8E9FGxbPksvBw==