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
- e75cc186986d8a8f3afb86c11355c653861a2b6c039fc0cc2fc5ca1f23c4bd0d
- request
- e9bfa90ef018035a97b2ebd1e156af602bc29c66744b367091be67969215f8f2
- transaction
- cbc23dadba7edcd2a41314a2e5c40d64365ed9e0f31c1f43398db1c792c634fdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36629
the chainentry 36629
- sealed to the entry before
- 607042ff62da96e7e801414ba52a0f7f43f031bc64f06e9ba2177e2084155820
- this leaf
- f83d6fd306c05eaab51f59a553a6cfc21cfec17594e4ad1cc647fc8ce749157e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +O/GqQA9gt38BX7E1om1unlfpeO0L7RIE6b2DY8LfKo26NzgC2/oNLrbC3e+wUcdil94BrhxqQc5OM//BSGbCA==