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
- 2977f4e834cefc008dfac6f117d2d8fc2da7777680c9a285b26ec2e855c6e171
- request
- e301e40c2b205facf313f4b6980e9f7fed32b579d93fed84ce60565fe913dd94
- transaction
- dfefb17d4641bf93e411247dc3de90b30f01f14cbe5b00a8a3d6cc9216a9c7b0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77560
the chainentry 77560
- sealed to the entry before
- b3adf68ac383323b9de589dcfd2d19fb3637db7cfd0e0a3df303aa0a67f0d788
- this leaf
- 3e26ffef0c4f0f11b4621165a22000e259c6059b7322dadbf2a8d8516982f612
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Gj7upwK0/r2QqTQJctmBTJKLXWiDN4wlhaQriJfcwWBfKYLIf+WrD05jGr1CIfP1oPS4PPTD1/umHKsBziXQAA==