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
- 25c5aa95b1ac03a44f28f2e99cfcccc179e0108701e99d0564333651163ce369
- request
- ef5f06162439eee11b1c3fe88a568e0557a3ff0059f42e060d86b86ec5d02d92
- transaction
- b59a199b67afd0aaa5828c8c5c6171d6e03314080fe65e88b5c2349cbb3c731ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67701
the chainentry 67701
- sealed to the entry before
- 279ba4b7b3d98c96388be8a179632899f2a031dd9d527c71972df6f327e2cb01
- this leaf
- 90cfdf19a5f501754b18c801b207bd3dc1b48e86c6a8296575b205b1f1b8def6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OdTfM6yxi99yHerE1gjc6CYFd7WF7H42Nk44Qsla5NP5AzJkeLyWglLNwa+KGzXoBjdjxDclFm8dGBuYgtTIDg==