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
- aa68ec803be6b8335d67054fa2c51703dd9e7aabe1005623a2d93cf7aaeeb46f
- request
- dc5130be574d1adfea4738cf29240d99a837c0d30dcddfe3788b61a9c59eff89
- transaction
- 408f021fe9ea22b64f4cd2786e7dcdda8aa7d5369b02faaabfb2fd1332a4fe24computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2170
the chainentry 2170
- sealed to the entry before
- 921eb15cf54d6fa458e884d0a18dad23c19f50918d8edd191270bac3dc7160d5
- this leaf
- 9e456ce6a9b248b2881525ffa12c1f47543b631e819092088f0dce66f3badc12
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3pXXhpgvEc4c8qt/inkHmPHHLoUGZFBVmv9ibJ1O+t3HdW9pGUD0crFv6/Wvt7z7zXKOcA+mhYEUCEZFtREKCQ==