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
- 1f18819ec235e087c991b9607d44154792362b658ab24e0cffc325ce434da5ab
- request
- 4fe0fea1f9d9cd5ad00bcacc2dbd638080c343014f051806a295a2afec84b591
- transaction
- 9a143d017b3da872474accff34a0238b04e0e04f680e60a28dd2da5d130a1aadcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72763
the chainentry 72763
- sealed to the entry before
- d9e5ab2522a38383b78e8550261a45c43d623a9b2437c9e70a1ff344633d8e2c
- this leaf
- 2dafbc83cba0931999e68c2d142c9f222e158882d90b51a029fe697fe9342ca4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MD0HQnG7CpZjEE2WAClpFgOo74so+SF7q8ZbD4piDOVfwoMvU3F8NrOx17+PP4gjdAoYG/O934YIdieSWcpvDA==