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
- 95b41fbae42ae87ea806503d96d31f4b50d1bc9183af039b6bbd31688144a8df
- request
- dbfa01054bc02ff914b7cf124367cba18bdabcc9bd00fce57977b940abcbfb9a
- transaction
- 5eb2b9f21df5eefacba0244505a72019afde8d7b09ba66d288e0dab89f888347computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32650
the chainentry 32650
- sealed to the entry before
- 3300d1a745318b853fe8a66e5f50ba8064bef21f1467f44669c3b0b627e581fc
- this leaf
- 82c1425dd5afbafafb4606559209f987bb843d510c2ae4e9742ddf4a75618dcd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- asc/HzT6YYwzlNzToUY+5z7gPvCo6L2YEdPjreQIuegDE16EkMengN85jT2ftLMifhlM5Ek0sEdA3rmxYvrhDQ==