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
- bda09082c479ad42a9b6ad4430638e4f6ef99e298dd41bd346b6587962c85ba8
- request
- 65cf305a51f34f1b680874cd30d42fae6642545d028af118663ebc6f18fea7a4
- transaction
- 37ba866c45e6b1d340ec658805ddfd2d6586719054b8e3c3c5d47de3113f419dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36
the chainentry 36
- sealed to the entry before
- adc66480879d8b94d44ae8666813f2adcd3a7bc568b67d6e1bd2c4fe696823d6
- this leaf
- cb42e13b7388274996df462a5d93d9fa7e25ad92dea0425e2457c94034916f68
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Mq8HZqbLDp0ul76L5zlKAn4sP+6kaY6S2dW0XWsfCCyQfiKpke9LA2lievLqNSpsUIjHlSmPn2ICx6oFlTsdAg==