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
- 359004d67ac1e4600f94c6be63e49f870d804e392ce913013771d055e6e434cc
- request
- 48043541623755f61807c3c49aec047ee8717a67fe9800aeeef61023ede61ad9
- transaction
- 29d2d1bdb2489bc3c37f922ece9851fdc079561c7985b3ba507411ab3bf88ac7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47579
the chainentry 47579
- sealed to the entry before
- 2f7dca0f920f47dbc35f5ca8834e63b9c58347c2e37a869f35a013f91881b6f4
- this leaf
- 26c8b820d4845eeed77b17de49cc4b7f80a243c4038e2d3f34096a3c42751fd8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hPwkEzAIIKtEDPzrqjtlXwmWKM4KbIsBfER0hsrrmDBvkZ2PYpcndygbizgPeazKg6W4nn0vpBwIwns6QzWhBw==