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
- 6f6d5814d954b2025a5be25b284624c6098167f1f31ad3aa3c251ab3bdd716b4
- request
- 6a4765de21dddf8fffe27cb578c9d0e611d7f65bbfe1a5ad1077865be0012c55
- transaction
- 4480dd345634741cfe4851ee855d87b9c7dc20d64d865ca81483f469cf723a16computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39240
the chainentry 39240
- sealed to the entry before
- 7e2321b651726b36e2732f100f26e810c50db89b6e9ab94d19353c5cf5e41b3d
- this leaf
- f65daf041efcea13a88bc399aab976d30adcab80383b4c8674f63fc3d86a421a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Pdy6rQf9EHYsTYGuuZm1mZGFz9YCxxHHVLtZ6u28sdF32Eu3DHmuhtFIQZtzanDEMbNn1Gr/KqmMA0oXugp+DQ==