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
- 4537b4f3b8cebd57e62d78edc2e550d003ad35ec50f3289db6095d78d763cb90
- request
- 87dfc7da91c3f64586ef53c680c948300e2b6b6a91752f42bef3a24a53ac1720
- transaction
- 21c32f922901feb0d9d63a3b2ccbd21a190694e9592a7113a10f99acfe30252fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75360
the chainentry 75360
- sealed to the entry before
- 6d4b793e60b55931e9a9e4ae6e4a2fbf1addf4b3a6c5fbbabd968c8e74ba3bac
- this leaf
- bf6cec66e8736ee2d97f157acf26d44a3905914c0fafc46cf01f87aab3bf7b90
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SYfWfih+B9vHdQK5OEPdt/UC9r3vYKLxuFxolPZ5vJ/wIhQ1qUHzVu2nK+fEWz1lu2F2LNkYQhMRHb5kuJGZCw==