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
- 08ecfd53066dad3ead21b8534df2de8bdb2f476c7292acb89c7fc390e0197216
- request
- 4a296b77722be0f8fb3903531d4da96f84624e132087d54deb55fc79f461aa34
- transaction
- 5af4dc543b998252642172a0813c8abbb59d3c247d4344972e924db70becdba9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56078
the chainentry 56078
- sealed to the entry before
- 143b878f0fe145fd54d8faf6c3227d75423dd753030b4928250044cf4d4e585c
- this leaf
- fbba219b48cbd00f0e358c473df4011a79932f34e8f29f5ac925714f84a1493a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BEvYfh7yT0fbCxorSCjkqx2mfXu/yxaJ+GV5VNdiUvs6tIeoLl8Elrjrn6M4+qkvikQncOpZCpMdQxsrWs41DA==