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
- 9fd7802e2106c21a4da2aede08f144de61a02532c48549c313d6472a4e46f6d5
- request
- ca8a8ab4164e0718a48335041edc3e9b9fd343fbbb6c50c740e818d3145078cc
- transaction
- aa5ede52ff93d77fe8986cb7c32ecda521ee449b551bc8273376672e183f920dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76174
the chainentry 76174
- sealed to the entry before
- e39469d235d8adddc82c40680531ccd8f0e71a660bf70d2602122babd1281f1b
- this leaf
- 5e89b72f771a94ad719c5f801985e6885dd71f58367f198c4c2feff617c812d5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oHAgSfvpZVCChS8O4+WQ5G23Q6fovouN3A/2IQYmHPNFbsKGqS3cBWINj/RdrrCYwqS+c4E11ZYC4ucSUMVTCw==