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
- 628145eef928030a2f84bdb44fb68488bd57d54d65b8532ffe39f303d11f0466
- request
- 4a947a713af3a088a33ab4139331397787c0f19b3f495a2325db60471b64974d
- transaction
- 1913e1c85527f5f64f5fa7dc6a264503080be308d4bd6724829a8cfec0c0290acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34573
the chainentry 34573
- sealed to the entry before
- 42cdef3c62b26fcc8ee32403c4ce72359510189b4ab98b2709a573ecb36defe1
- this leaf
- 93ea68a21d1869e9838f1b0486c003d656153ef2a468fc14cbb92dae6f1956da
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rjRVNe8nTWHRNjV09f3x+2S8r6VpXLrCpvK9fypxC5z4JB+UVQUw9ES60hZ15GYQZi3y0ssRYRdUTk2sQwMpAg==