2017-01-02T00:01:09+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:07:37+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:07:37+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:07:37+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:07:37+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:07:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:07:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:07:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:07:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:07:59+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:07:59+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:00+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:00+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:22+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:22+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:22+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:22+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:44+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:44+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:45+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:45+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:56+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:56+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:56+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:08:56+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:07+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:07+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:07+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:08+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:18+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:18+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:30+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:30+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:30+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:30+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:42+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:52+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:52+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:53+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:09:53+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:04+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:04+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:04+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:04+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:15+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:15+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:15+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:16+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:27+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:27+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:38+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:38+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:38+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:38+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:10:50+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:00+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:00+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:01+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:01+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:12+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:12+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:12+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:12+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:23+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:23+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:24+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:24+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:35+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:35+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:35+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:35+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:50+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:50+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:51+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:11:51+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:02+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:02+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:02+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:02+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:13+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:14+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:14+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:14+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:36+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:36+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:37+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:37+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:59+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:12:59+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:00+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:00+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:22+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:22+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:22+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:22+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:45+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:45+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:45+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:46+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:56+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:56+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:57+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:13:57+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:07+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:07+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:08+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:08+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:30+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:30+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:30+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:30+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:42+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:51+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:52+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:52+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:14:53+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:03+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:03+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:04+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:04+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:15+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:15+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:15+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:15+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:37+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:37+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:37+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:37+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:59+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:15:59+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:00+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:00+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:22+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:22+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:23+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:23+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:45+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:47+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:47+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:47+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:47+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:47+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:16:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:09+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:09+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:32+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:32+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:32+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:32+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:55+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:55+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:55+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:55+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:55+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:56+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:57+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:17:57+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:17+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:17+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:18+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:18+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:18+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:18+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:20+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:40+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:40+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:40+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:40+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:42+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:18:42+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:01+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:03+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:03+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:03+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:03+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:03+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:05+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:05+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:28+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:19:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:20:07+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:20:07+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:20:08+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:20:08+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:20:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:20:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:20:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:20:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:20:43+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:20:43+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:20:44+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:20:44+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:01+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:02+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:02+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:03+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:20+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:20+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:21+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:37+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:38+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:38+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:39+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:56+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:56+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:57+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:21:57+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:22:14+10:00 INFO (6): Forcing to https. URL: https://new.wyndhamvrap.com/wmsp/payment/finance 2017-01-02T00:22:14+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:22:15+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:22:16+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:22:16+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:22:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:22:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:22:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:22:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:22:51+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:22:52+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:22:52+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:22:53+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:23:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:23:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:23:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:23:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:23:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:23:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:23:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T00:25:43+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-01-02T07:13:32+10:00 INFO (6): Created payment: id=23305&full_name=Philip+Lyons&email_address=&email_receipt_sent_count=0&owner_number=00073003273&amount=634.76&created_ts=2017-01-02+07%3A13%3A32&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T07:14:04+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=82021&callback_status_code=&restext=Approved&fingerprint=dd26b514c7945296a5826e33b5c9802251bab57c&merchant=WFQ0110&refid=00073003273&pan=376064...001&summarycode=1&rescode=08&txnid=643453×tamp=20170101211332 2017-01-02T08:06:57+10:00 INFO (6): Created payment: id=14838&full_name=Sheelagh+Henson&email_address=&email_receipt_sent_count=0&contract_number=000711401687&amount=5000&created_ts=2017-01-02+08%3A06%3A57&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T08:08:24+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=102019&callback_status_code=&restext=Approved&fingerprint=623fddd63a3c197dd08b424f06dd66cc57a32106&merchant=WFQ0010&refid=000711401687&pan=413542...022&summarycode=1&rescode=08&txnid=653469×tamp=20170101220657 2017-01-02T08:17:54+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Amount - redisplaying form to user 2017-01-02T08:18:21+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Amount - redisplaying form to user 2017-01-02T08:18:51+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Amount - redisplaying form to user 2017-01-02T08:35:58+10:00 INFO (6): Created payment: id=14839&full_name=Gopal+Mall&email_address=&email_receipt_sent_count=0&contract_number=001101619781&amount=3000&created_ts=2017-01-02+08%3A35%3A58&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T08:36:56+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=112020&callback_status_code=&restext=Approved&fingerprint=bb03c475465b5b0da1a38f90ca11d1e7a0fe6446&merchant=WFQ0010&refid=001101619781&pan=534276...300&summarycode=1&rescode=08&txnid=661304×tamp=20170101223558 2017-01-02T08:50:15+10:00 INFO (6): Created payment: id=23306&full_name=Geoffrey+Alway&email_address=&email_receipt_sent_count=0&owner_number=00078000476&amount=634.8&created_ts=2017-01-02+08%3A50%3A15&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T08:50:52+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=12017&callback_status_code=&restext=Refer+to+Card+Issuer&fingerprint=2995c091d420ccae50630ed3d5774011addab834&merchant=WFQ0110&refid=00078000476&pan=377767...417&summarycode=2&rescode=01&txnid=668272×tamp=20170101225015 2017-01-02T08:52:35+10:00 INFO (6): Created payment: id=23307&full_name=Geoffrey+Alway&email_address=&email_receipt_sent_count=0&owner_number=00078000476&amount=634.8&created_ts=2017-01-02+08%3A52%3A35&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T08:53:10+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=52020&callback_status_code=&restext=Approved&fingerprint=b8e7d6c490b374853370e4b378f8176a076ee55e&merchant=WFQ0110&refid=00078000476&pan=377767...417&summarycode=1&rescode=08&txnid=668412×tamp=20170101225235 2017-01-02T09:02:50+10:00 INFO (6): Created payment: id=23308&full_name=Tracey-Kim+Querevalu+Parrish&email_address=&email_receipt_sent_count=0&owner_number=00071003944&amount=195.3&created_ts=2017-01-02+09%3A02%3A50&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T09:03:50+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=12017&callback_status_code=&restext=Expired+Card-Pick+Up&fingerprint=aa6661ad90ee192a49260911ec34e19377c23c7f&merchant=WFQ0110&refid=00071003944&pan=439242...929&summarycode=2&rescode=33&txnid=674309×tamp=20170101230250 2017-01-02T09:04:25+10:00 INFO (6): Created payment: id=23309&full_name=Tracey-Kim+Querevalu+Parrish&email_address=&email_receipt_sent_count=0&owner_number=00071003944&amount=195.3&created_ts=2017-01-02+09%3A04%3A25&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T09:05:23+10:00 INFO (6): Created payment: id=23310&full_name=Tracey-Kim+Querevalu+Parrish&email_address=&email_receipt_sent_count=0&owner_number=00071003944&amount=195.3&created_ts=2017-01-02+09%3A05%3A23&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T09:06:04+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=112018&callback_status_code=&restext=Expired+Card-Pick+Up&fingerprint=ca9f84f4266057870a1bc368097e42cea4983d64&merchant=WFQ0110&refid=00071003944&pan=439242...929&summarycode=2&rescode=33&txnid=669297×tamp=20170101230523 2017-01-02T09:38:17+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Full Name - redisplaying form to user 2017-01-02T09:38:34+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Full Name - redisplaying form to user 2017-01-02T09:38:59+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Full Name - redisplaying form to user 2017-01-02T11:17:44+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Full Name - redisplaying form to user 2017-01-02T11:17:54+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Full Name - redisplaying form to user 2017-01-02T11:18:17+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Full Name - redisplaying form to user 2017-01-02T11:18:19+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Full Name - redisplaying form to user 2017-01-02T11:18:27+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Full Name - redisplaying form to user 2017-01-02T11:18:34+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Full Name - redisplaying form to user 2017-01-02T11:19:09+10:00 INFO (6): Created payment: id=23311&full_name=Hugh+McGuinness&email_address=&email_receipt_sent_count=0&owner_number=00072001538&amount=1061.03&created_ts=2017-01-02+11%3A19%3A09&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T11:19:29+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=52020&callback_status_code=&restext=Approved&fingerprint=ae5bdb1fc93db109b7c58d4c0d0e1ff91755f1a4&merchant=WFQ0110&refid=00072001538&pan=456472...398&summarycode=1&rescode=08&txnid=719345×tamp=20170102011909 2017-01-02T12:47:15+10:00 INFO (6): Created payment: id=23312&full_name=Neville+Yee&email_address=&email_receipt_sent_count=0&owner_number=00201070911&amount=195.3&created_ts=2017-01-02+12%3A47%3A15&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T12:48:20+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=12018&callback_status_code=&restext=Refer+to+Card+Issuer&fingerprint=bd956f2257abbc647ab2da8b81f47693ef957a15&merchant=WFQ0110&refid=00201070911&pan=376085...009&summarycode=2&rescode=01&txnid=758311×tamp=20170102024715 2017-01-02T12:48:53+10:00 INFO (6): Created payment: id=23313&full_name=Neville+Yee&email_address=&email_receipt_sent_count=0&owner_number=00201070911&amount=195.3&created_ts=2017-01-02+12%3A48%3A53&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T12:49:36+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=12018&callback_status_code=&restext=Approved&fingerprint=d710f9e094d4755fc7d898f84b119262e899f4ae&merchant=WFQ0110&refid=00201070911&pan=376085...009&summarycode=1&rescode=08&txnid=758489×tamp=20170102024853 2017-01-02T12:53:12+10:00 INFO (6): Created payment: id=23314&full_name=Neville+Yee&email_address=&email_receipt_sent_count=0&owner_number=00201070911&amount=195.3&created_ts=2017-01-02+12%3A53%3A12&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T13:02:42+10:00 INFO (6): Created payment: id=23315&full_name=Theodore+Kalaitzidis&email_address=&email_receipt_sent_count=0&owner_number=00075000840&amount=15869&created_ts=2017-01-02+13%3A02%3A42&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T13:03:54+10:00 INFO (6): Created payment: id=23316&full_name=Theodore+Kalaitzidis&email_address=&email_receipt_sent_count=0&owner_number=00075000840&amount=158.69&created_ts=2017-01-02+13%3A03%3A54&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T13:05:09+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=52020&callback_status_code=&restext=Approved&fingerprint=15e7ff1cfd2612750265ee888a9527f600696417&merchant=WFQ0110&refid=00075000840&pan=544637...614&summarycode=1&rescode=08&txnid=763420×tamp=20170102030354 2017-01-02T13:34:21+10:00 INFO (6): Created payment: id=23317&full_name=Andrew+Gladwin&email_address=&email_receipt_sent_count=0&owner_number=00201302984&amount=85&created_ts=2017-01-02+13%3A34%3A21&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T13:34:58+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=92017&callback_status_code=&restext=Approved&fingerprint=1ca1be3923f34c831cda103890d01f1456f80e25&merchant=WFQ0110&refid=00201302984&pan=377878...265&summarycode=1&rescode=08&txnid=778076×tamp=20170102033421 2017-01-02T13:59:12+10:00 INFO (6): Created payment: id=23318&full_name=Frances+Jean+Mitchell&email_address=&email_receipt_sent_count=0&owner_number=00076003718&amount=231.91&created_ts=2017-01-02+13%3A59%3A12&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T13:59:50+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=22019&callback_status_code=&restext=Approved&fingerprint=6fdf7f8a8f5319532ad3c5ab67075256e728a459&merchant=WFQ0110&refid=00076003718&pan=522980...510&summarycode=1&rescode=08&txnid=783109×tamp=20170102035912 2017-01-02T14:00:06+10:00 INFO (6): Created payment: id=23319&full_name=Adi+Susanto&email_address=&email_receipt_sent_count=0&owner_number=00073003570&amount=778.08&created_ts=2017-01-02+14%3A00%3A06&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T14:01:20+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=72017&callback_status_code=&restext=Approved&fingerprint=73585c5667f43b78faf2ada0f75fb2b2346ccfaf&merchant=WFQ0110&refid=00073003570&pan=379229...916&summarycode=1&rescode=08&txnid=781429×tamp=20170102040006 2017-01-02T14:21:42+10:00 INFO (6): Created payment: id=23320&full_name=John+Ronke++&email_address=&email_receipt_sent_count=0&owner_number=00201021101&amount=300&created_ts=2017-01-02+14%3A21%3A42&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T14:22:55+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=92017&callback_status_code=&restext=Approved&fingerprint=bd20c83047018daf0c3a05ebacc86a04e21fe993&merchant=WFQ0110&refid=00201021101&pan=519244...737&summarycode=1&rescode=08&txnid=791103×tamp=20170102042142 2017-01-02T15:26:04+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Owner Number - redisplaying form to user 2017-01-02T15:26:49+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Full Name - redisplaying form to user 2017-01-02T15:27:08+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Full Name - redisplaying form to user 2017-01-02T15:27:57+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Full Name - redisplaying form to user 2017-01-02T16:29:30+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Owner Number - redisplaying form to user 2017-01-02T16:29:59+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Full Name - redisplaying form to user 2017-01-02T16:30:46+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Full Name - redisplaying form to user 2017-01-02T16:30:55+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Full Name - redisplaying form to user 2017-01-02T16:31:25+10:00 INFO (6): Created payment: id=23321&full_name=Barbara+Walker&email_address=&email_receipt_sent_count=0&owner_number=00201328848&amount=158.69&created_ts=2017-01-02+16%3A31%3A25&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T16:32:41+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=82019&callback_status_code=&restext=Approved&fingerprint=5c7661526568c2512e9e2658857d1f7d59cc4414&merchant=WFQ0110&refid=00201328848&pan=528596...673&summarycode=1&rescode=08&txnid=841454×tamp=20170102063125 2017-01-02T16:50:43+10:00 WARN (4): Invalid input for levies payment submission: Invalid value set for Owner Number - redisplaying form to user 2017-01-02T16:51:03+10:00 INFO (6): Created payment: id=23322&full_name=Michael+prakash&email_address=&email_receipt_sent_count=0&owner_number=00201327392&amount=158.69&created_ts=2017-01-02+16%3A51%3A03&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T16:52:11+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=122020&callback_status_code=&restext=Approved&fingerprint=8abb04ab3f2c4ca5d8284cece85f701f236d0cbd&merchant=WFQ0110&refid=00201327392&pan=376064...005&summarycode=1&rescode=08&txnid=851220×tamp=20170102065103 2017-01-02T18:58:11+10:00 INFO (6): Created payment: id=23323&full_name=Amanjit+Singh&email_address=&email_receipt_sent_count=0&owner_number=00201379697&amount=158.69&created_ts=2017-01-02+18%3A58%3A11&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T18:59:19+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=82017&callback_status_code=&restext=Approved&fingerprint=9910ee4c2c3a17d1f9b07e8d6e56a3718f08f93b&merchant=WFQ0110&refid=00201379697&pan=379229...999&summarycode=1&rescode=08&txnid=900779×tamp=20170102085811 2017-01-02T19:52:42+10:00 INFO (6): Created payment: id=23324&full_name=Mrs+Marie+Catherine+Lee&email_address=&email_receipt_sent_count=0&owner_number=00201090017&amount=374.12&created_ts=2017-01-02+19%3A52%3A42&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T19:53:31+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170102&expirydate=112020&callback_status_code=&restext=Approved&fingerprint=2ef8c1e74ba68a4faead192fd6c09e6187d0d350&merchant=WFQ0110&refid=00201090017&pan=377852...781&summarycode=1&rescode=08&txnid=921666×tamp=20170102095242 2017-01-02T22:15:17+10:00 INFO (6): Created payment: id=23325&full_name=Kevin+Wang&email_address=&email_receipt_sent_count=0&owner_number=00076000851&amount=231.91&created_ts=2017-01-02+22%3A15%3A17&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-01-02T22:15:41+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170103&expirydate=32020&callback_status_code=&restext=Approved&fingerprint=88f3ae3dd83c682a69231e8cfc65821307cd7e34&merchant=WFQ0110&refid=00076000851&pan=376074...007&summarycode=1&rescode=08&txnid=977187×tamp=20170102121517 2017-01-02T23:24:14+10:00 INFO (6): Forcing to https. URL: https://new.wyndhamvrap.com/wmsp/payment/finance