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
- 9e6f0e2a11480182b816bc02442cc2478d414dc80e0b6329bf32072a9965b5af
- request
- 9eb278d2fea551436e5b7db294a1f5a4cac2e2e869b9b84c00b032b1a19612bc
- transaction
- e316db0f0807059b6521a2a9e52b748e8cae2dd6f638fb5db5c604d2652b828acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22756
the chainentry 22756
- sealed to the entry before
- 19586c06b7c709d17794a2a0e49cc78f6e465152a68f5e6e444eb8d35ea8cf0e
- this leaf
- ab47a3ae1bd37cb702077900ab3d59892f8b466bb95a1be92ddb158506340d39
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +hYi3sS268rglknfdrR7eCKkIaanD9S5mlSESVNvfjrG86t5a7993164WPyRCkrdIQZLTdr1mDGX78dRPaArBw==