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
- c2e090a67e84482bdf585837d8604d7867f59824b467e0b99b14a9a5f8becc1b
- request
- 22ebe6e71fd7f539e20d8b7bbd893be6c9f3f8b401f759dfc84fa995ae94233e
- transaction
- 02568010f2b7434d0f6bcad55e38cc905178fb176bb0ad3ddc391dee6522bf55computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68914
the chainentry 68914
- sealed to the entry before
- 33b9b73c47ed02fb488bf6d6093e5f9d33e6bf8e3739a0dd8edf4ec4e1b95f23
- this leaf
- fa1d47d91a87aa7a117dea2966ce8f617a943eee34a15e48064673396faba660
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6sqtB0ehsWW9sA7WO5LPYHh0n8ZUV0kGXBrOdPSuaJO+NcRAzPtiQlXnyc5AgUapz4uh8A8oFGITvnA9n4GXAA==