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
- 499c3fa1be13eabedb2d26e2f340e14bc3bca00407a1322fa6fee8ecd6622696
- request
- 5fc64c27b6cd1f88c44d68cf16b64f720a22cdb47618c03d59685ce19b2732e8
- transaction
- ab32700aeb06cc97d68dcc03c258b958ec7b8a657646cba41c6f807695c690a6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65913
the chainentry 65913
- sealed to the entry before
- b5914a38b9310da939f1b236faaf12e1542589fc4a1480d8830f7b7d41ecfb3e
- this leaf
- 87fcd2c3a24809024f7b873fe7e5dcac8f52460ffe2253e8c1e4037c48d04696
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4CFCjVcxGV+61S2pJCpWRX6e/XTD5yRXn3pu2o+FIbMpU37tNELE2funXIK4XNtss3HhFhj7+r22Ux17bIxNBQ==