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
- ac6ed4d627ada8fb39d7064d1f4a570a5df028a4172e5a31245e9e91de6c3cf7
- request
- 17f68eb771000f78a4a1be1b3b919fc7bdad521fa0a5ac48274df9538e329bd7
- transaction
- 8791fb0dbcbca6664e6ad4286f004ff2ee0722cc35dd39a266c0b15918fb1f28computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74926
the chainentry 74926
- sealed to the entry before
- 3c50ecd2763791447c11bef7833a19c3edbcd6ede5eb3b98868f2b0a1cb0859b
- this leaf
- 79f51df74bb098cc2e961af979e75ccc2865ad6c300e6e80210f9fdb37aca676
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /brJZICQub1JQGyPyMOovP0Aokj8HNcmIkC9CI2eDcfoIy+hrCG0W6yYjRRoLXv2WWdOJ2GKskWNO1UDJm1mAw==