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
- 9847ec19fe0c476814045fe67a5ecd87b695d886973d737c2262a2ee548339c0
- request
- 7da38ec8bab9ffbba66f0084f450d9ea80fa21e35d30b7c0d206f4281820bc54
- transaction
- 795ecf51f8046d3e9377dd7481554db9f272254ce78634e70c1ef995fa25c492computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48989
the chainentry 48989
- sealed to the entry before
- 7e550a8400592800adf85c68a673a187208db90ff543196a2545455fa7524d13
- this leaf
- 94f3b99f437ec33b5c065a969021d3b08e6849c5ae1b3b00ad7959546d48b72c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oNf0FLU0LDWlpjc9cwrTkfMi9mAjV+edHPKY/NDTD32pBZqNQGWkEFYhVqvoBYjEPDsUTF1XpV5yjQc0QHRqCg==