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
- 202ed56705ed014c536641b68e5fe8e99ec9479a8e0c1cbecf8924f4715ff470
- request
- 514ff5431e665ab5543b165da7456f175ca91def62598e9818015d2be182a5a6
- transaction
- 11ad5baab105e05ccaeb78eef9843ee8bcd1a41a73ef8a86644d6f1f74fd26ddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22633
the chainentry 22633
- sealed to the entry before
- 75f2749856ee3f4df6c0aafdd07a1532f478798c047c8ffa7d8ccda244977a1c
- this leaf
- 97d18bb18c29208b55fb80bd1bf3816e18293dd5faa008bbb3b668852ee13855
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wfJwLkWysf9qLzJrS1O+QhJyBT6+MkQ3RemOAjIK5ZB6r60+UJj0OjS+tNiNpQQdfvb1Gr7v7rlXEjZBHA6UCg==