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
- 05e9210753f4bc955830a2b71f4c8557afd6f18a6dbb803d5144637fbd54f4b2
- request
- 128c511b00b0f12a853f99f6e226d644dbe13066eb0a5f50ca64645b367c24f6
- transaction
- 042d804df55c3704c2a8ed76cf324e1ebf05f4d6c704c83a1c4043467ba64af5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68376
the chainentry 68376
- sealed to the entry before
- 47f222af0220b1b111662050d919a0c57f1830d414e436a8cd7b3017d6c7b26d
- this leaf
- f6f01965c882936b65d4635088ec3f862592c5260774ac2b3505143d716f8434
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hMQ1HyYESpBMKUPG1gjSNFrVlFwAALCAJ8bBN6UwuwFyRS8DLt0+aPKvLWdaLmV4Ai2Frc0rvZU/1SiyllZlDA==