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
- ecb1a8f68e512819ea82ed9666126e9c60e8a0bc8942c320bce4601dc6184258
- request
- 965b2cb4d9e24955afb4a55e2ce78e1160ce638dd73b5d23e839305a1b0ffaa8
- transaction
- e3495cf77a42d3859a1fbeef00113be1861eb8725a34931b189a063eb4e8e4c3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9519
the chainentry 9519
- sealed to the entry before
- ffb82e3cf82c723cc885a53d0869d85bac4d5419c96b2bc32fef833a1eba2969
- this leaf
- 55b5efffe06e2afb491d020e5cd107a03ac53aea0ccea09679a4880aaf996548
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ldol5pglX642f+5qSX3LsBs/LF7VJ38E9uCvEPwEAfwvuI2gRe4QZ0Q/+Q2eEHAd9/59zJVZlwcCpnamE9knAA==