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
- 15c5228cf65e2ef1cdb91ffe1aa183a5513a9830a064dc50d5cd0a8949f1e007
- request
- 3c362d60207b9c1e349745f6b7636c0db352a0d23225a75c49cf8fb8af0a7430
- transaction
- f3daef205dce4440ecfcd41388a674c34b91db927941dacc84babd6cce5a8306computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19660
the chainentry 19660
- sealed to the entry before
- 096ac4ae7e2a219fa507f382f4d833f91118b1203c716d1bda357ebca8a025ff
- this leaf
- 6d1f799a897dc75252406654ca3e23e25ec4b59aaaef94a7731d2b13e6bc12a3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Y1blEoOXSSrcw2IuHPeIvG6Z1hI+9iZWnKbopYTrmXFZWB6l7bfHYbGMzq4VYMwVPW2EwaWt86PCpncBROltAg==