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
- 6fcb6f4e9a50524c513ffc64e337d65b9887af295c0e89ad84a5ee26e794136a
- request
- 2195a96e01fe254fc27fcf285bf682770bb5f67bfeb8a07205e3719c14c7fa36
- transaction
- cdb2d4403e5bd5d7a93c0c9383fd62a0e200eb37ddba144d0c723137067cb9c5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6055
the chainentry 6055
- sealed to the entry before
- 6606edf7159d8a9a0539c58bbba0bb992eb29e076c6747ea144036c64bc8ab9a
- this leaf
- 6db9d54dec148c111a541ae0e3c982f17d9672425f5f7f0a50b46a98984f7346
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qBsBc3vAsEyftjguBJfEIqSy4zbUYCqNbnBQRK8TzaL/H7mi23G06uktY7wp+arBAeEPpCm+La3V3nD4W+OoAw==