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
- c6b9be46aa61767bdb17998172dcf3938b20be1e7b8c2438a31026ce1376fe27
- request
- 50cfd57983e17be1f8f1718249ad3c18ad8f2442feeb1f267588af20504668d0
- transaction
- ab78c466b701794a26d02e92423186f7770317d42f000a7688ae857fefe3f3edcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41698
the chainentry 41698
- sealed to the entry before
- a9eae5889652ee5cda0cbcb30e54cf739ce67033c439444ea2c7934e17340e3e
- this leaf
- 4eac5066e7f47850519f8ba9a00f41c3f160c64b7fc4d892c3159367c378f14f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oJUaZQO7+ISlrrEAyPMJ6ptPK19jqPvL907ose3FtgF1fHuTKQQPCvOgtMtQk4A3kAR/uVHLR285it75uZVjDw==