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
- 3535a6e777546d6db08eaa2323eb824bf295e4498d64430f481f7141621449bc
- request
- 01cb88ecdade9933e65ec5cab0321622b50725180acf17c25aa9fb06746439bd
- transaction
- df401c096dfa3187b59d06bd843c205c0a3056f8288ceb5dc28055a4d6608d2fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63079
the chainentry 63079
- sealed to the entry before
- 5de759045133a777d5b5a9652b66f921c50ab541a75e89d767f19993e2fcaeec
- this leaf
- b658c8777a47ece76e7ca2065b7742624e0b4cf2caff62c57bb85ea78791d459
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4/iDr6UgHC+YkOJ6aqgztJ8/KgZu4eGErxKLeMVmEysfEsmMzxdhwA5QcvOAa518RnLQjaujlW+g7AxcSaC3Dg==