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
- 01aa5eec3f679894fd95d58e28aaeceefbd194a39b1565b7b53f6f7ed6e6e881
- request
- ad04dcbe4806af50a63970b931277ee5117b7515c079c7af7d1ba7549b45f87e
- transaction
- 5816e7bf4b61a620686e78d76ce5e5f82e439b16a9bbead611557f1ce658ab34computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41958
the chainentry 41958
- sealed to the entry before
- 8178b43eab60090bc8f4b33e5da110eccb80c0cee2f6fb416dee8621411dffe3
- this leaf
- 0f20a7c4379cab2aa1394dca8b0a89c7225c84ff216cae0099da4950d8dd7811
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LCK+l8WCHpL+QWw0pLWnDlhEaQbDwjJHU+ZLxwawwbcbss0m90MowobqkP1jm3rlkkiZqB4SB844ooJw+mO5AQ==