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
- 4cc2584868334abb81c87492350fa4d7f8aaf840386b318329a15e6ddfcc4c02
- request
- 1a303817a55994920c7722ae59b3b01e7b748cc7508c01417daf666bfc93f0ba
- transaction
- 38e0be5c46b9ee5b87619b890ebd2976d2564109c02a9d658fdbd2694056433fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43360
the chainentry 43360
- sealed to the entry before
- 6f4f96be85798b0a994d292a295d07c6f49374cfc7bbe36633946f0508d9db00
- this leaf
- 97f8fa9538448767da3e6025c1410626feebc353a43abb5a69229c62d0afba1a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oXw6fRql5QRCI+uRKLJTh57jvQR4+GgTubdYxg3yrUPmJP65w3YeW57C433XckMAt10NKfjOGAhxcrvHeSuYAQ==