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
- c25f0f6470da750947d205072ec8925b2c451657c58097a53fdc7eaab96638d8
- request
- 3bf7887f52428f6bd33bd9493d1913e35645168af7175a45db8b8ff68f92b172
- transaction
- 423eca06a4372cf9d8947d7df6c10090fc512d90b047f2d30d1a8959ec4a0e77computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73962
the chainentry 73962
- sealed to the entry before
- 4c2434769e892b962cf330653e9c3da77fdea0f838c0fa089355f234c4f8fbd4
- this leaf
- 80247cee66bb9439fa3bbddb075838f3ace43d7d1b2024fb740e26f07a5d1671
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9ijegXeFqoITSxN5uADvCdm4HGz2LK6f/0gWjvtpGKvv+HvMOmyGAKUo1kyCtSMrGEr3UZWdldo0pFibYALjBw==