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
- f6db06fb642fe75d88e16caf4f450cd51093c5192ed6995c96d1b6510a38ddf6
- request
- 3267e9468cf9c76ebdc0b1c363aa49473133509fd5d0abf91950892d30015d3a
- transaction
- 85993eede6c9da5d1f19d222200b23f30883d705796a69d90d3ec85360c7366fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72462
the chainentry 72462
- sealed to the entry before
- a2a4260c0141c05e281660e957e67e25b57dc530ef6ccd0a49341c16543ce5a1
- this leaf
- 2214a95b0986c269325aa48149319ca453e934513d695c374f5012c52eb2474c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uxweV2HH4jZZfjhGj2XojlHbCu9X8tFa7wSQLl6taDwXvmmFUHC2JR2kLeDmjrfT9Vl72HyUSb7wsBc44/WvAQ==