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
- 82ce02ed3c47b7c7a84c3466ec92769a4c05311ac78ffb4f1759b1a53f65d631
- request
- 173bd032b00c601124f421cfb0857dd682b5bb18bb915465dd0ba459ec9488af
- transaction
- a80d6cccbb9633c74b53473e63d5ecc99b10d1bf329351a2d7dfde923b8b89f5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30201
the chainentry 30201
- sealed to the entry before
- e397d0409bcf305a85c0712f3ec1b56f41c8f80ff3aefde5faa80ca6a7a0b6af
- this leaf
- 56790248f3178761fe8ec7d2b83ac9c395377ea103ad2b9a937c3577e9a3f3d6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TZvp++BezIzXMd3Q4mn9uEybyBd4d36NNnvOcVXFPkoRkt4qc2xpNhstFMBUzeX5vkmH6x22IrkclarXJjQiCA==