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
- fdc6221f1f6b0ea348ac2875a597837e98dc4a68fa87b5bede28dd42df338f33
- request
- 4ec63fed7a04d33ef0364a89d2134845f9ce0a9aa02a535925004a5486170322
- transaction
- c4123143252b91240b6263b50703001b11dde34620f26fdfb33546c43a80ea92computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61953
the chainentry 61953
- sealed to the entry before
- a212cbda9d84148147a99abbb3a9dc1b5bb49dd5586c27d108035daffcd82ec7
- this leaf
- f4c33361bbbcd4d6962bbcc7bbd2bfe0cda7e463de7855ce5a45d3dfd5fa967b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yjVpTcmjnYyEOYd82KmRYiTOuA+GqD7Ek9vfTb3B3EVYcVbzO1PZUr+vKTa6hu1FZE6F7CKH1n+jvlQGBuIlDg==