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
- c393260dd4385a824e5e8b36c0a0a4ad7eb21e98b16cfae6b55d3189a3dd2f3c
- request
- 9c6775f23f8d696177e35167fa74a50fd8bd0090ceb6e7ff1c8adb905e186208
- transaction
- 9b241d54f97422974977fa67b7bfe33093d7c61ef53566da68efdcefff967c20computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16283
the chainentry 16283
- sealed to the entry before
- c7b693e3226deb2af693e72fcb5d8e44e0a32a06e5e6f77053edc89692d33d5b
- this leaf
- 0d1852c0a9f54960099f085d1b0cdebe8fbaca19d64a0af947b4ba883df342e5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cpxB/5JQI04iJzn2M1FZ9as7SAhhsJs0oL6+jGNrrc+fg3hdcKVNuJmlLqsF75kEWEGRdKsNQpvmzCZPnA6KDA==