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
- deb0f41b184fcba18314ac8b34a4c40890ec49a8f3da7615125ab9193e7aeb88
- request
- dfdf64efe8034e504aa97b6d16d6fbe699938f3730408e64d85ea53b7e6e8295
- transaction
- bfb9ccaa434dd389904b6bae7d62c72c5a1fcdd620d650353550feb48e823dfccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43761
the chainentry 43761
- sealed to the entry before
- 3678d877e6e8143478fd1f53adab3edce4ee4383f98bcd060fc14fe0eb9470b5
- this leaf
- 45bb6111ac4c5de7a5856f60f91d62a90d0631ab91a47d99488bb0272ff000b2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- C99Go8KdJElYRzFSRrRJIzFpiyD6WXMc6yWjUmyLvzwqMR0R8d7yTrBytGdRu0j6xjmgiSMJ2SdNXM+KSey6Ag==