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
- d9468ac8175d39557d9edbd23ab132f8328ebb3525bcda6eee85df00387d037e
- request
- 61a36098197d6b1af6c681b87a5b4da7b0f89a1205a96c65291d4b39032233c1
- transaction
- 3f89430b168d29a62b519cae341cef1e469dc4d6c236cd09ec307cf0be9f702ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43371
the chainentry 43371
- sealed to the entry before
- 87457b67d73ba65dc11149200d8d2702d7ddcc3e2af14c28091affb7c0f78565
- this leaf
- 3c3206857f216603f1fa5d6eac200809b51b454c201e94aa8f4d1f7decfd0a16
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9Id2lDgS9v3BYyel8Xs49XYfWcrIq3mgk+SUnjLlvvJ52gAS+Pp3Iq4jpxw4+57S/wwL++pOwtmLQ1isE1T5BA==