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
- a8530c7bd9183e62e1b61b164e64d0933c4cc3e84346ee0f1fb7fcd7688c9321
- request
- d091215605d5b2bb41f38430d765cdbac9094bfdbd5cda5f90ec7793bbe20d11
- transaction
- 9af04c956242eb0ab8d120f1e67362add888550d8d076ba2f72767017895cbbacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29203
the chainentry 29203
- sealed to the entry before
- f29bf1446e016c967f714b7768b87073e1aa85b954a404dfa924de598754a0a8
- this leaf
- f686e9c71da8396b1b20b632ebe26eb155d925935c6c6468cd33764bd8de8b9f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JTeB9IUmrrx/VdIvYCB7SYfn7tJwmtZLUqt70DqozSVEo3pidE46TJ1p6QcFx0A4e1/p4fFAzpsun3t0Y0tDDg==