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
- 8854371f0e3e0cf7f413a4b5b9fd4fff5197aa83fe88798ad4a9b813439078fc
- request
- 8b47bacd067490debc5fb1ff0b8c4b30f315938ad603750c5d20596e876346f7
- transaction
- 3716dc566aff04baf2cab6efa03b298e9db4853f116d84da67bee8c9e390ceefcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27647
the chainentry 27647
- sealed to the entry before
- 324ca7b74ba845cbc8e826faecb0982efa653869c5259fa06e731646cc7aacd7
- this leaf
- cfa0c971d5464d8548aaa37dd43114f8e600be5f24ab9d16bc02a296c1fc2cf4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c0egLiSiW9SX/L7a615yefHhRLuKvps0Kjz6DBM+5QOR3GE70dsrKx3UfkBAo1CED3RAyIVpYB8rRN7adSPeCg==