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
- d69b3e08219aafce7bcf914cd63244e56b7831fb62a6c9e89c608f27965c6ddf
- request
- ee070b8ece09ae8d0be8ef9b17dfcef816c236c7722c89a00330c1cead33eac9
- transaction
- 5f0adb2733c9732736c609419b2ae75bc3c49c6d66ed07ef5ba4590dd06f7f98computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36372
the chainentry 36372
- sealed to the entry before
- 64ddb62be4752d06cd970c24eb626981ae6fced9dfb53aa7f16cdf94c44a123e
- this leaf
- 9acd4d700b90b2296f19a5242854e5159c4aceb08e4e1721beb51dcdbaf3661f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 58JX587AMM1TXDbUG8lDOqRP1W3MWByPkZ5X5RQ6CUg6tK3ktX4ORLSwiVYM2Q9zGJV5vsFr1CwnQ5TTrS8nBQ==