One-Time Payment Notification

The error messages in the One-Time Payment Notification inbound web service are as follows:

Table 6-1

Message Category Message Number Message Text Comments
11001 106 Length of value <value> (in bytes) too long for Field Account ID. Maximum length: <value> Found <value>. (11001, 106) is a common message number where the specific field name is a parameter
11001 106 Length of value <value> (in bytes) too long for Field Service Task ID. Maximum length: <value> Found <value>. (11001, 106) is a common message number where the specific field name is a parameter
11001 106 Length of value <value> (in bytes) too long for Field Payment Event ID. Maximum length: <value> Found <value>. (11001, 106) is a common message number where the specific field name is a parameter
11001 1850 Input request field Payment Type has an invalid value. Invalid Extended Lookup value <value>. Valid values are for BO C1-PaymentTypeLookup (e.g. 12 CREDITCARD SAVINGS ...). (11001, 1850) is a common message number that has parameters for field name and the reason that the field is invalid
11001 1850 Input request field Payment Amount has an invalid value. Invalid numeric value <value>. (11001, 1850) is a common message number that has parameters for field name and the reason that the field is invalid
11101 401 Service Task ID not found.
11102 10423 Payment Date/Time is required. (11102, 10423) is a common message number where the specific field name is a parameter
11102 10423 Payment Type is required. (11102, 10423) is a common message number where the specific field name is a parameter
11102 10423 Payment Amount is required. (11102, 10423) is a common message number where the specific field name is a parameter
11102 10423 Routing Number is required. (11102, 10423) is a common message number where the specific field name is a parameter
11102 10423 External Account Number is required. (11102, 10423) is a common message number where the specific field name is a parameter
11102 10423 Credit Card Type is required. (11102, 10423) is a common message number where the specific field name is a parameter
11102 10423 Credit Card Number is required. (11102, 10423) is a common message number where the specific field name is a parameter
11102 10423 Expiration Month is required. (11102, 10423) is a common message number where the specific field name is a parameter
11102 10423 Expiration Year is required. (11102, 10423) is a common message number where the specific field name is a parameter
11102 10423 Account Number is required. (11102, 10423) is a common message number where the specific field name is a parameter
11102 10423 Service Task ID is required. (11102, 10423) is a common message number where the specific field name is a parameter
11125 10001 Third Party Payment Processing Integration master configuration not found.ent Process service task processing script not found. No action needed from third-party payment processors. Issue is caused by internal config.
11125 11013 This Tender Type <value> should not generate auto pay.
11125 11006 Unable to determine auto pay source. Please check Routing Number.
11125 11019 The system cannot cancel a service task already processed for cancellation.
11125 11020 The system cannot cancel discarded requests or requests in error.
11125 11028 One Time Payment Cancel processing script not found. No action needed from third-party payment processors. Issue is caused by internal config.
11125 11030 Service Task (<value>) does not exist.
11125 11031 Payment Event (<value>) does not exist
11125 11033 The payment linked to this service task was cancelled through service task %1.
11125 11034 This service task is a cancellation request for service task %1.
11125 11035 The system cannot cancel a request for cancellation.
11125 11100 Third Party One Time Payment Add/Update service task processing script not found. No action needed from third-party payment processors. Issue is caused by internal config.
11125 11102 Unable to determine One Time Pay service task type. No action needed from third-party payment processors. Issue is caused by internal config.
11125 11103 Payment Type is not configured as one of the Accepted Payment Types.
11125 11110 Payment Amount cannot be zero.
11125 11113 Payment Amount is invalid. Incorrect formatExample: non-numeric or incorrect precision/scale
11125 11114 Only pending one-time payment can be processed.
11125 11201 Payment Event (%1) Payment Tender (%2) - Invalid Payment Date/Time %3, expected in format yyyy-MM-ddTHH:mm:ssXXX.