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
- aae3eaee170af20fc52e13697f82c80b6b15cba999e49b2026eb398a35950ff1
- request
- 1d02e4a7ed96e0c1d61e6a9f16b719ed9a56e8156de1f64d1890d298152240a6
- transaction
- 17606e0f2905038ba86315b66c2823da27ddb6aad2f488ed2650000f5054fed7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38763
the chainentry 38763
- sealed to the entry before
- 437264795b9d3b249cf01fc60e197c2fc83a218019ee1dfe825af878b597fb42
- this leaf
- 0a05e151870734bf3fc8ff1b3a865c0b93717b476b7d46cc44fc4f0c5f2cae23
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ijLP7ueX1ryD+RH9hifEXHTzx4c2Obx85LgQqvqFdDtLyQobzm6uldgi8O4I9jful5d0bZPEf/Rgjwg20JizCQ==