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
- a1b215497516a7d2d32e089ec7365393276736b2de69ef4e669d2d2b89b10acb
- request
- a292b96ecc6409e5f55a97544a5c1e0a0bffceac9caa2643c173a9bcf60fdfb7
- transaction
- eb0cbec66edfea3b34d73d341a08c9e897a8f805eac2e001feae2d5c886b24facomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69207
the chainentry 69207
- sealed to the entry before
- 2647da47f966149750346d932f8c33f437d4f1ef4d80f505f0cbe7063a37f615
- this leaf
- 4de2df067a46962e7fe4bf2dd00773aa7a9d1fcc9a28f1915d067d4c66d08654
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Vx9MbRqxl3HOsLV3qMHeT50Ck0AHLKrWF5BH0FMOxVXnqzhiDkB2k3DACxGnfOnefw4Uy5YA12kmDBuyIqyHCg==