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
- e85deea9f1c0ffbd192321ab11f73008d7b9553f71729581216ef89d532eeec4
- request
- e81728a3185aa3f151f9bbd6d06f1c59e2662fb1b40452219aa51cef7a0ba9c3
- transaction
- cfe83b40197dc7442ea9ce7bb99884c219c39ec4957cd11cc6764700dcda5bd3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60786
the chainentry 60786
- sealed to the entry before
- 4ae125a63716451bb8cb83c13b6267c2af098e9d0511f97f33c1afcc2df47c3b
- this leaf
- 1015b0935f1f6b5c69dc626122653e45b8b652aea7c8cba619e0eb0938a3f5fd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dzMZaOEZBx4UMMIAv82CFIwKKMimmAf5IAQXNXVM88lRtyEjEEAWjIasoOV1/vvC+TMQJ87cKiM8Kr5CbPGHBw==