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
- 79fd67719c82f1526393a03e1250b9af2d4fdebd582d0c33c0906d5aaa224211
- request
- 35e0ea4cd365b11ce5173872e55f177fb13c7d38ee16900f353842e045ded91b
- transaction
- 13450b5f5f170d00306a528499bdb1a1176db5729d48f29b2b41f01bfe844251computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19476
the chainentry 19476
- sealed to the entry before
- 886943ea5e7cb13533b35ec43a01015212a1d373f851e92aaa159f8bbf50fbb0
- this leaf
- efd3e729c0e08b996996445ca7bf5d487d5aaae257ffc697d00436c66d0ec946
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iEWqWMmuk9Yo+G5cJUQuvwjJLO1r07ucZ82BmzXNy5tpILvjS+G9T9MAUhMSkpp+DCVfhyYgE0wbKG/c0ZytBA==