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
- b5f64300d87e3c50261b874b21422f6e9149c3eb1280d31be769519aace2e916
- request
- 10e62f8e3dced9d50e1c0403eea98762d6bb1a04802378f23f91fc3057eacc35
- transaction
- 4b78dda9247269533e36939ce7d8ec1689da8181224e3a22a0fd0ae34604ca1bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74890
the chainentry 74890
- sealed to the entry before
- db627729f6fe9bdf181f933c75c0906ea6bd2117c5061afa134eada843d37e4c
- this leaf
- 9845d01088e0942be8d5b48f6b3eb7941d10169f5c8120f85deea062770477fb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F9FYfNMkwON+lfK8kjmiPhD15yie2P5nU6ytOog2loiVuuc7zvmFKCuw7sDS5BnWDoP4+6TgnPDVwdxot31vAA==