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
- b3822c6c97480e3e966a6ee3bef5a4b0df899b8928ab877ed196f064013def5e
- request
- 2a3c38be02a50235357b476c83a79efdd3d0cbca87aead61ec14d150c35ff0ea
- transaction
- aa4fad4a8f3c80c61250027803e8627b57453a61715309de5152aa8fc7038461computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11631
the chainentry 11631
- sealed to the entry before
- 9c2786f40c6bfd3768580b619d3134765fe073d7e5a0976b18d4b0f4766d9cb3
- this leaf
- f5f07f993c128d441c5a2faf2511822e109007c98794f3a023be395432a7441c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- z0MGf1ZQ+B4l8aptXt8tbx8Ga7/JAEt8DwKsOSn1NmIZyJHUXFGrstxEOqFMF8myDf23r8Ovs9umwaQ7hW+3CQ==