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
- c1ff35659a6a1fe3ca884709603eb38018eb6838d155d0822d1bb8239d08f332
- request
- 678e5ca510f3fbb4964d3e2b5356243b5cfd78d44bbcedf1fa9833aaea08c095
- transaction
- baa0e9770629689e12c064dc61476845d6dd32185bd739b60704c039c06c36b6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20958
the chainentry 20958
- sealed to the entry before
- 2660e41b61ccd65dfed1938d0973e98303203b4ba85ed1116a3c1c2b05f30ca4
- this leaf
- 8e40904c0f61771e842b5ec6781186c7f3a26f78d38ccf205fdc86ec524c3398
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0fGpC8ihsKE6M/fNTdAkCbDEM7J5TgG2oRsDm22TuE6Gyt/QiE8YgX6ARjr8bqapn+2qnl+ytpRCw/CRIXF2Ag==