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
- 705df058083bee71ecc4ba20ffdf3415b17bbd916c90650e0e2c1b8f265c4d18
- request
- 9d7662fdc522c0f69c5132919e3d31040e43f8eb23216376857f68688da422eb
- transaction
- b27b48bbb4330766bfa304ad7077dfb1e9737fb5f9b43d25bd41106c1b982da8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52128
the chainentry 52128
- sealed to the entry before
- e55ccaac6afa915056be015ede919af414a9b48779a1625ee7f4c73fcafa3198
- this leaf
- 9d498b561cd66c826bf40618da66901af654271d58a9ad35aaa81aef97a4f1c3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B+/+IlFM8r64FYB7JQP55opgjy/mMk8fbSdesSiTkrpP2wZmc/oOSNrVETkuHZKfmqGl5XD0Bh+nbBSAqCkJCA==