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
- 958af811de6c21f39eef313c8c24693ec1f6db8b7f506a27f765eeac5f2fff9b
- request
- a197b5b9cacb0192e1befd501f6fe4988ab16a1f4cee3c9e4330cad9ca7e391e
- transaction
- 97e5e9def6c548a0e7047955625e334cd0e49646191a2c966288f7c53d5766b5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65921
the chainentry 65921
- sealed to the entry before
- dabc86d123b7b0b8d99b48304003e1af8b693913cda545755e47ae2b398bcf3b
- this leaf
- d1619233e208815585128318c6b6a0b68b740b80754a1730dbc8cd21fbb96097
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1AyJHPH7pWi09uWTBHUHslbKOR9nHOFN1L4zPCMfuAT8e/yIayK4Zyq/Takyoc0iFaE/6sauRRZMFv+Qu3ibDw==