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
- 58d7f6ef82e7344a7a1e44974c3bf603a4c5d423f4c37577b4a28cd589f59772
- request
- 40f088b2e0ceb38bb624da2cc20b715c9d0ca25720fb7b0b254989e9b3343791
- transaction
- ba6cc6868bd89f9eb0a0654fb1b03290da8081a60fb906a456eef09b6ab71195computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74085
the chainentry 74085
- sealed to the entry before
- 4815944e1cb36c13b4763913e5921ca9ad368b94e2075fa5075183c0def62cf2
- this leaf
- 18aa3435ed43a0439084f2ad8b1d7d6da06c1040ccf59889d2814dc979ef4453
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DOe0HxYGUAXDvF2Q2Nquir2QW9hzolGWpR4C4zMFiddI8WCjuUnhoIqIRSOn0HUHltb+XVCOT3s5IIASD8jbAA==