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
- dbe4f58edc9355c05cd85ab22becc20eb0a26989151216a1a6cbad24f7e2a8e1
- request
- 01f90d097a0a7715cc1e865a99ae59850b919f17f96bb4a540198c39d747c1ab
- transaction
- 97abc5db2d98adc56780fdf5fb6466816e70a4ac333d9e5024e408edeb9d0dbecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15289
the chainentry 15289
- sealed to the entry before
- 2eeca8fc3752d5cd406e660c264a50b63f68e8de4be8d040a824ca067e1258dd
- this leaf
- 3968d342d4eaeddddc6454e230ec8512d5fe77264690dd2310ce7971f9a6fac0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KsuQ59HrtJEDYDZNPO8Ccd4lfcWvPWReTTcLrwMNJNh9ZNVham2gTF7JNC0sSYpOPeu6oR7tNKISE/kgvGASCg==