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
- 81459fe3108ae7d921ec4c842cfa59d0cfd4b20e983a35d38e472536cb4de312
- request
- c178e03028c33b566493ad0329f12e0863deb9e0ad13573bd7166bd6c31ea9ab
- transaction
- 09f943cad4be3d6d9acaab47777af4c5241b7d9c209b7e9e94565f472dc375f4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52622
the chainentry 52622
- sealed to the entry before
- 65f2c9481cd34abe2e1ec6a872080262a1703ef01183647bba583ad68d824a0a
- this leaf
- 4eac17cff09f3ff5cd13c2e8658947bdc11d1bf73eb1abed4503021fd8a1f50b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rIvlHOKU4a5zg6fguPY4nkF3q5IXUiJRySfgh/+QOBOLq4DekwjoX0J3ESQjtoSZvpkDk8dS5h9WeNredLzvDg==