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
- c61db34d37a903acdc32d26493882e1ba7d0eaf23eec02723b42ec3cbef4e0d6
- request
- 9b6c452d546278d86925b3bf492fc9015414745d727e92b6519a74f5883d71db
- transaction
- da0ed04b3730a6ab36307346c319ad56791250ad69fb0d82dce8b6b1d8e31f0bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21545
the chainentry 21545
- sealed to the entry before
- 7192ddf641f5a3a646bb92fcc38040e49e4aeac923c04047b050085e8f3e8a7a
- this leaf
- c9309dd4772295d5c3e027ae1759399008babbceec7f9ad1b257f0b58d07443e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6RcxU/hZE0Q8ntXZMDaMgtU7vwXTImqDz9sJOie9c13Ib2KY0Zn0udErTJ0sjN1XO8FkuxvGVXiOq7kd7XBzBw==