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
- c49ced0e2499ffd6724d80e540ed3eb59698aeeaced06a5997436f288576e347
- request
- 58f9ef9f7108c5c17e288c2b4cf3d04e247633cf2164f293bd4a7460ebc1dfcc
- transaction
- e9f6ac888f35177337a11062ea88a1aee583011f74fb24be8096ca50091b2f84computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50336
the chainentry 50336
- sealed to the entry before
- c0eccb9bb2a310f75b335ff62278384a21f69de733e556dbdfd9f9dca445f0a0
- this leaf
- 045e1f46a635ff80c05d6fbb01f060ad7b74a1508678060e9ee54fc44305f9c5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vqpveIhqJUJYY8K2ojkTUiWbjoIOWo6e6YKBabKCHO6d4NOpX+lR/IJB7eA/+nrH0aFVIWWm4wCIViCLF+scDg==