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
- d9649e3c0a237396c76ea34990ce1fbecedccc08c7bcb9a753d063027250c2bc
- request
- 49f1afcd3bf6de089a5cfe6556c4c7362f5dc600057a16bbf67358d673ed28de
- transaction
- d24c823c902f1fa6bad9707385f279abec22ee7d6e5e56564eabb68cd5ec35d3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1800
the chainentry 1800
- sealed to the entry before
- 07a5e591a79214ac1b4a4d68cabc65297ea089c4b8c25ee39d97995aafd99874
- this leaf
- 4d292ddb4e8a6298096291e824cd4e59fe3caa1134eb63cd1243c8f3c93a012c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EZ1zFMbO42EMX4imaJRRC8vqESG4KgM2PTwb8TAbeUA41TGddh66i1CsUskdJgppMvO5Q0hhcl7j2fM07V45Dg==