2017-02-02T00:25:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:32:50+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:32:50+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:32:50+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:32:50+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:01+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:01+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:02+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:02+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:13+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:13+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:13+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:13+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:24+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:24+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:36+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:36+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:36+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:36+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:47+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:47+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:47+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:47+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:58+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:58+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:59+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:33:59+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:21+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:21+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:21+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:21+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:32+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:32+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:44+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:44+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:44+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:44+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:55+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:55+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:55+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:34:56+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:06+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:06+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:07+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:07+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:18+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:18+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:18+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:18+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:29+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:29+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:30+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:30+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:52+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:52+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:52+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:35:53+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:03+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:03+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:04+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:04+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:15+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:15+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:15+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:15+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:27+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:27+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:38+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:38+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:38+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:38+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:50+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:36:50+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:01+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:01+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:01+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:03+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:13+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:13+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:14+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:14+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:36+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:36+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:37+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:37+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:59+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:37:59+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:00+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:00+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:22+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:22+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:23+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:23+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:45+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:45+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:46+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:46+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:57+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:57+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:57+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:38:57+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:08+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:08+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:08+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:08+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:20+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:20+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:31+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:31+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:31+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:31+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:42+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:42+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:42+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:43+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:53+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:53+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:54+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:39:54+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:05+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:05+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:05+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:05+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:16+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:16+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:17+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:17+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:28+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:28+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:28+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:28+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:39+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:39+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:39+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:50+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:50+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:51+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:40:51+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:01+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:01+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:02+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:02+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:12+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:12+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:13+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:13+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:23+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:23+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:24+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:24+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:35+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:35+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:36+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:41:36+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:01+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:01+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:02+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:02+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:02+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:02+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:03+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:03+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:24+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:24+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:24+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:25+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:46+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:47+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:47+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:47+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:47+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:47+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:48+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:42:49+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:09+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:09+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:09+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:09+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:31+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:31+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:31+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:31+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:55+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:55+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:55+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:56+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:56+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:56+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:57+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:43:57+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:18+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:18+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:18+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:20+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:42+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:42+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:44:43+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:03+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:04+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:04+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:04+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:04+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:04+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:05+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:05+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:23+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:23+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:24+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:24+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:41+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:42+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:42+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:45:43+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:00+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:00+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:01+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:01+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:18+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:20+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:37+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:38+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:38+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:38+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:56+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:56+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:57+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:46:57+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:47:14+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:47:14+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:47:15+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:47:15+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:47:33+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:47:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:47:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:47:35+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:47:52+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:47:52+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:47:53+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:47:53+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:48:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:48:10+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:48:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:48:11+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:48:28+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:48:29+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:48:29+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:48:30+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:48:44+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:48:53+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:48:53+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T00:51:04+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T07:04:31+10:00 INFO (6): Created payment: id=23658&full_name=Leonie+Easterbrook&email_address=&email_receipt_sent_count=0&owner_number=00201567784&amount=61.14&created_ts=2017-02-02+07%3A04%3A31&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T07:06:12+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=22017&callback_status_code=&restext=Approved&fingerprint=22889c1e5ba7cc3a6ff14d6f5db4731bc175caab&merchant=WFQ0110&refid=00201567784&pan=516361...831&summarycode=1&rescode=08&txnid=457808×tamp=20170201210431 2017-02-02T07:09:18+10:00 INFO (6): Created payment: id=23659&full_name=John+Harraghy&email_address=&email_receipt_sent_count=0&owner_number=00201957030&amount=115.88&created_ts=2017-02-02+07%3A09%3A18&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T07:09:45+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=102020&callback_status_code=&restext=Approved&fingerprint=1cf61766a35dc3de92689db9ffca7dad68437710&merchant=WFQ0110&refid=00201957030&pan=456432...411&summarycode=1&rescode=08&txnid=462450×tamp=20170201210918 2017-02-02T08:50:27+10:00 INFO (6): Created payment: id=15045&full_name=Jodie+Hannon&email_address=&email_receipt_sent_count=0&contract_number=002581502333&amount=200&created_ts=2017-02-02+08%3A50%3A27&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T08:51:16+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=32019&callback_status_code=&restext=Approved&fingerprint=aa74f3926987afad66984e848debed5fc85b079d&merchant=WFQ0010&refid=002581502333&pan=401795...211&summarycode=1&rescode=08&txnid=510063×tamp=20170201225027 2017-02-02T08:54:39+10:00 INFO (6): Created payment: id=15046&full_name=Jodie+Hannon&email_address=&email_receipt_sent_count=0&contract_number=002581502333&amount=1050&created_ts=2017-02-02+08%3A54%3A39&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T08:55:45+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=72019&callback_status_code=&restext=Approved&fingerprint=01804c0cc0862facbec8234fdea1f72297bc16d5&merchant=WFQ0010&refid=002581502333&pan=532655...005&summarycode=1&rescode=08&txnid=508522×tamp=20170201225439 2017-02-02T09:02:29+10:00 INFO (6): Created payment: id=23660&full_name=Lynne+Chelo+daguplo+Trinidad&email_address=&email_receipt_sent_count=0&owner_number=00201619637&amount=301&created_ts=2017-02-02+09%3A02%3A29&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T09:03:36+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=82017&callback_status_code=&restext=Approved&fingerprint=f1827f933cd8e0a5f38bb6177530da724c19eaad&merchant=WFQ0110&refid=00201619637&pan=462949...394&summarycode=1&rescode=08&txnid=511827×tamp=20170201230229 2017-02-02T09:25:10+10:00 INFO (6): Created payment: id=23661&full_name=Martin+Saffrtett&email_address=&email_receipt_sent_count=0&owner_number=00073001973&amount=173.69&created_ts=2017-02-02+09%3A25%3A10&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T09:25:35+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=32018&callback_status_code=&restext=Approved&fingerprint=2da993187a63814d903e20266d77c4991adad51c&merchant=WFQ0110&refid=00073001973&pan=521729...547&summarycode=1&rescode=08&txnid=528458×tamp=20170201232510 2017-02-02T09:26:34+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T09:26:38+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T10:09:51+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T10:43:07+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Contract Number - redisplaying form to user 2017-02-02T11:30:59+10:00 INFO (6): Created payment: id=15047&full_name=Test&email_address=&email_receipt_sent_count=0&contract_number=000711700963&amount=1000&created_ts=2017-02-02+11%3A30%3A59&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T11:38:12+10:00 INFO (6): Created payment: id=15048&full_name=fernando&email_address=&email_receipt_sent_count=0&contract_number=000711700963&amount=10000&created_ts=2017-02-02+11%3A38%3A12&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T11:39:19+10:00 INFO (6): Created payment: id=15049&full_name=Fer&email_address=&email_receipt_sent_count=0&contract_number=000711700963&amount=10000&created_ts=2017-02-02+11%3A39%3A19&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T11:39:36+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Full Name - redisplaying form to user 2017-02-02T11:40:04+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Full Name - redisplaying form to user 2017-02-02T11:40:44+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Full Name - redisplaying form to user 2017-02-02T11:41:15+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Full Name - redisplaying form to user 2017-02-02T11:42:19+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Full Name - redisplaying form to user 2017-02-02T11:42:52+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Full Name - redisplaying form to user 2017-02-02T11:43:51+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Full Name - redisplaying form to user 2017-02-02T11:44:26+10:00 WARN (4): Invalid input for finance payment submission: Invalid value set for Full Name - redisplaying form to user 2017-02-02T13:26:52+10:00 INFO (6): Created payment: id=23662&full_name=Indira+Naidu&email_address=&email_receipt_sent_count=0&owner_number=00076007398&amount=173.69&created_ts=2017-02-02+13%3A26%3A52&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T13:27:22+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=42020&callback_status_code=&restext=Approved&fingerprint=70345abe9314392ab6a92be07caa9ba761427151&merchant=WFQ0110&refid=00076007398&pan=552350...760&summarycode=1&rescode=08&txnid=685308×tamp=20170202032652 2017-02-02T13:39:51+10:00 INFO (6): Created payment: id=23663&full_name=William+and+Rhonda+Horne&email_address=&email_receipt_sent_count=0&owner_number=00079000208&amount=107.96&created_ts=2017-02-02+13%3A39%3A51&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T13:40:34+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=42019&callback_status_code=&restext=Approved&fingerprint=eaa34919ba4e26916fe47c082073fe6d876993e0&merchant=WFQ0110&refid=00079000208&pan=443441...805&summarycode=1&rescode=08&txnid=696255×tamp=20170202033951 2017-02-02T14:09:33+10:00 INFO (6): Created payment: id=23664&full_name=laura+martinez+vinhal&email_address=&email_receipt_sent_count=0&owner_number=00201848112&amount=60&created_ts=2017-02-02+14%3A09%3A33&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T14:09:57+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=92018&callback_status_code=&restext=Approved&fingerprint=30e3ac2ee671b7e87f350e02d4c7f86af8ca24ae&merchant=WFQ0110&refid=00201848112&pan=521729...789&summarycode=1&rescode=08&txnid=705656×tamp=20170202040933 2017-02-02T15:24:02+10:00 INFO (6): Created payment: id=15050&full_name=Mr+Khaled+Atyah&email_address=&email_receipt_sent_count=0&contract_number=000781502802&amount=15065.5&created_ts=2017-02-02+15%3A24%3A02&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T15:32:10+10:00 INFO (6): Created payment: id=15051&full_name=Vicki+fuller&email_address=&email_receipt_sent_count=0&contract_number=000781602446&amount=5000&created_ts=2017-02-02+15%3A32%3A10&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T15:34:15+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=32019&callback_status_code=&restext=Approved&fingerprint=d17b90bb1e1ade441afde081f73346839579d42c&merchant=WFQ0010&refid=000781602446&pan=455702...669&summarycode=1&rescode=08&txnid=750213×tamp=20170202053210 2017-02-02T15:59:24+10:00 INFO (6): Created payment: id=23665&full_name=Nestor+Ventura&email_address=&email_receipt_sent_count=0&owner_number=00201226681&amount=15&created_ts=2017-02-02+15%3A59%3A24&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T16:00:39+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=102019&callback_status_code=&restext=Approved&fingerprint=bf905ca2b971c6e9e1b7d1fc724d5c8f7c850f14&merchant=WFQ0110&refid=00201226681&pan=456469...520&summarycode=1&rescode=08&txnid=764036×tamp=20170202055924 2017-02-02T16:11:44+10:00 INFO (6): Created payment: id=23666&full_name=Amanda+ward&email_address=&email_receipt_sent_count=0&owner_number=00203178893&amount=155.79&created_ts=2017-02-02+16%3A11%3A44&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T16:12:22+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=22020&callback_status_code=&restext=Approved&fingerprint=26405a01ea90b77377f61328b14c0be435fbbf74&merchant=WFQ0110&refid=00203178893&pan=377767...464&summarycode=1&rescode=08&txnid=768947×tamp=20170202061144 2017-02-02T16:18:24+10:00 INFO (6): Created payment: id=15052&full_name=Alana+Corowa&email_address=&email_receipt_sent_count=0&contract_number=000791105711&amount=50&created_ts=2017-02-02+16%3A18%3A24&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T16:19:09+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=52020&callback_status_code=&restext=Approved&fingerprint=ddb372773c706b90a6b248a1aa7cb003a8f5ec34&merchant=WFQ0010&refid=000791105711&pan=401795...903&summarycode=1&rescode=08&txnid=767987×tamp=20170202061824 2017-02-02T16:49:29+10:00 INFO (6): Created payment: id=23667&full_name=Franklin+Joyce&email_address=&email_receipt_sent_count=0&owner_number=00201776518&amount=278.88&created_ts=2017-02-02+16%3A49%3A29&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T16:50:18+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=62020&callback_status_code=&restext=Approved&fingerprint=8fd4279fd3e6938a9b407b1c0b540b997254a901&merchant=WFQ0110&refid=00201776518&pan=401795...615&summarycode=1&rescode=08&txnid=794812×tamp=20170202064929 2017-02-02T17:12:46+10:00 INFO (6): Created payment: id=23668&full_name=Daniel+Foster+&email_address=&email_receipt_sent_count=0&owner_number=00203309146&amount=119.98&created_ts=2017-02-02+17%3A12%3A46&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T17:13:37+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=12018&callback_status_code=&restext=Refer+to+Card+Issuer&fingerprint=3bc75f854feef843c695c4aed89c0703d39045e2&merchant=WFQ0110&refid=00203309146&pan=456432...056&summarycode=2&rescode=01&txnid=799687×tamp=20170202071246 2017-02-02T17:15:51+10:00 INFO (6): Created payment: id=23669&full_name=Daniel+foster&email_address=&email_receipt_sent_count=0&owner_number=00203309146&amount=119.98&created_ts=2017-02-02+17%3A15%3A51&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T17:16:37+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=52018&callback_status_code=&restext=Approved&fingerprint=d95401fec3ad1cfa1fa59069a5bc84a9279520ec&merchant=WFQ0110&refid=00203309146&pan=456432...056&summarycode=1&rescode=08&txnid=799983×tamp=20170202071551 2017-02-02T18:19:25+10:00 INFO (6): Created payment: id=15053&full_name=Matthew+Tibble&email_address=&email_receipt_sent_count=0&contract_number=000701602054&amount=6000&created_ts=2017-02-02+18%3A19%3A25&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T18:19:46+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=52020&callback_status_code=&restext=Approved&fingerprint=e44bf7e52961c3ce5b903249f6dd7cff53927a16&merchant=WFQ0010&refid=000701602054&pan=522980...311&summarycode=1&rescode=08&txnid=829188×tamp=20170202081925 2017-02-02T18:25:03+10:00 INFO (6): Created payment: id=23670&full_name=Warren+Radloff&email_address=&email_receipt_sent_count=0&owner_number=00079000814&amount=173.69&created_ts=2017-02-02+18%3A25%3A03&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T18:25:45+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=12020&callback_status_code=&restext=Approved&fingerprint=d63aafe5fd1e19a992dbb2d34e49ab3efe24968f&merchant=WFQ0110&refid=00079000814&pan=456430...321&summarycode=1&rescode=08&txnid=833385×tamp=20170202082503 2017-02-02T19:19:49+10:00 INFO (6): Created payment: id=23671&full_name=Lesley+Heidemann&email_address=&email_receipt_sent_count=0&owner_number=00074002817&amount=167.92&created_ts=2017-02-02+19%3A19%3A49&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T19:20:31+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170202&expirydate=92019&callback_status_code=&restext=Approved&fingerprint=0b8516ae87373da481a7f7085a3430f84a8c38d7&merchant=WFQ0110&refid=00074002817&pan=377850...484&summarycode=1&rescode=08&txnid=859935×tamp=20170202091949 2017-02-02T21:08:37+10:00 INFO (6): Created payment: id=23672&full_name=Raymond+Thomas+Carroll&email_address=&email_receipt_sent_count=0&owner_number=00076004485&amount=173.69&created_ts=2017-02-02+21%3A08%3A37&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T21:10:04+10:00 INFO (6): Created payment: id=23673&full_name=Nicola+Barraclough&email_address=&email_receipt_sent_count=0&owner_number=00203144556&amount=52.74&created_ts=2017-02-02+21%3A10%3A04&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T21:11:11+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170203&expirydate=112018&callback_status_code=&restext=Approved&fingerprint=48611814b43b85cdb2ee7bb42c955d8f1b26005c&merchant=WFQ0110&refid=00076004485&pan=521729...441&summarycode=1&rescode=08&txnid=914937×tamp=20170202110837 2017-02-02T21:12:10+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170203&expirydate=122017&callback_status_code=&restext=Approved&fingerprint=2d713d70f8644eb480e00a9e5e937ecc44c8f29a&merchant=WFQ0110&refid=00203144556&pan=401795...792&summarycode=1&rescode=08&txnid=909623×tamp=20170202111004 2017-02-02T21:15:20+10:00 INFO (6): Created payment: id=23674&full_name=Raymond+Thomas+Carroll&email_address=&email_receipt_sent_count=0&owner_number=00076004485&amount=173.69&created_ts=2017-02-02+21%3A15%3A20&payment_status=waiting+payment&email_notification_sent_count=0&email_notification_error_count=0 2017-02-02T21:15:38+10:00 INFO (6): NAB return request: module=wmsp&controller=payment&action=return&settdate=20170203&expirydate=112018&callback_status_code=&restext=Approved&fingerprint=2572936d944ae5b9557b1544e970d59598959fe7&merchant=WFQ0110&refid=00076004485&pan=521729...441&summarycode=1&rescode=08&txnid=913517×tamp=20170202111520