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
- 380df78db4422923fa03f269d8f1e0ca6128c403c2ec748bada6962ad7162fff
- request
- 95e2519932c3bd5f44e0ab2c175d7839f4cb36c661c18e7527479ef37e76d5d3
- transaction
- 395ecc106c9f9a21a0d386f258b7f4fc76d9865e8f4d08f01653dea04bd004accomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66619
the chainentry 66619
- sealed to the entry before
- 951cf06c446dc16e9c3d8a44c8cc30dcfbb764de298cd22da22c568909fa54d8
- this leaf
- cc9f09ea148e95dfb6f48c5f48e007e07601b1954a439baac8923bdb9f699715
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ppy292DE8VsF2hbhVs3KcSGQ8nB+RRz0XEqQJKQUwOQZKhCH3/LyD/0tN11B78CB2wff8Z2WRyf1AkUa1xRCDw==