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
- cf24739ec3ec707da73499b216f6caa46a1f0bbba718c9ac399eceb74da12b00
- request
- a62335e347ea8bbc5b99f65b3adbe8eeaf9b913f98d6a5c24b686b89d25b6518
- transaction
- b2df73b3c1a2ebf4a510c45abd125dc53b2404392fe58b46d5c39f283acef86ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11442
the chainentry 11442
- sealed to the entry before
- f228c773e0fa709030ea3308c0386f87f9d332bf3da7c54ae7c022c28017429e
- this leaf
- 24430be4276731b18f3c497a54b858231d036c05d12eb90d4307db50a06bf5e4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ieKJX+vkHKUH8zHbA1iXhPiAVjMWKBHEnXTPEIuDRJUYoO2W9JDtzJZBBZ2TvKEDy4ptHfjroajDAKbVuwRyDg==