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
- 0e8a54891a6d6c18b76cd01069c4332a598e0a8476800b759f5cffa871b97d57
- request
- b72047299992d634b79af8358f494c66d983fc39c27a4e93c08b6dec3f249d96
- transaction
- 8469ce46a5832b8ffc4dbb80b0488e167d22067e9137a2696e755b0766de9cc4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76610
the chainentry 76610
- sealed to the entry before
- e703ac318be18508260f3d87a54c78ef969bdfa6c45e5f5eebaf3b655ea65eff
- this leaf
- a6aa1028e81243717cea9a964a8e3004608ccb10fa75ae8a3198162140793fad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- h71UklTjQ+22JlQcC/zhe9pUg8YL518Aw8f/bPFumkbLZxZOCm+YBQnbgIOgccExO6tNlrI28aoh/DUussGUBg==