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
- 95c4c55025b08177c88f2390d36e4e044b36363ece8f7143699ab1fe3e910bd1
- request
- e90ef055b2944e1ee4954e314f9982804a9ac13c66356b9b0815d3b6ffce7a93
- transaction
- 42c85cc4e85a19586dd37f4895179cd9d570289e6c1064840155b03ba0c20f55computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74001
the chainentry 74001
- sealed to the entry before
- ae7928da786d31a5c4daeefdf8305f748b2b1b7c43e70d2eba69fec3003e988a
- this leaf
- 5749462610fa68c51f6a9f86c467de255d7bffafc52aaf433149045afb4a06aa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ur7esrsyJWJHaH0f3I/2WMq/dx3ZJtopIkOrwmULlOVfDgFK8aDJGWdKIUL2kSOhow+rUYjhlOESnw0P/ztWCw==