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
- 389ad5a71b8dfca8cfec34c6965c84d3d10015fe857496334d69764b255eed13
- request
- 1a696ec005a1e2c663a6baebaee5bbac17736fc23f8efb234185a688e6807835
- transaction
- 1e374ce93ebdcd81684d29ee9a29576190cd017581f4b7d10e84ae01e4b5969dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28144
the chainentry 28144
- sealed to the entry before
- b6976dc5fc6fb8d4ec6a6998361c418d4f786cd461e48ef2025888780f5d4c74
- this leaf
- 92e6f54c019c8c9f6fd927389e54fe9878f9711e797967a92217d1ad80204206
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EmNAy0DO43uAVuJbLJSNJICRDxLkv8mNOIVN48/0M2qp62UCu9qVrEakcIU069hrdYLko9C2G+njSbuzgpWBAA==