Error Codes
Payment Schedules Error Codes
Codes returned by Payment Schedule requests (TYPE=L). Always read TEXT along with CODE — several codes cover more than one situation, and TEXT says which.
For errors on a StartSession that includes SCHEDID, see Hosted Payment Errors.
Schedule Codes
| Code | Message | Description |
|---|---|---|
8300 | INVALID SUBTYPE / request format error | The SUBTYPE isn't a schedule action, or the request couldn't be read. TEXT describes the problem. |
8301 | DUPLICATE SCHEDID | A schedule with this SCHEDID already exists on this terminal. |
8302 | MISSING INVOICE | INVOICE was not sent on CS. |
8303 | Varies | The payment couldn't be added to the schedule. TEXT gives the reason. |
8304 | INVALID PYMT DATE / INVALID DATE / MISSING REFNUM | A payment DATE is more than 30 days in the past or more than 365 days in the future, or REFNUM was not sent on an action that needs it. |
8305 | DUPLICATE REFNUM | A payment with this REFNUM already exists on this terminal. REFNUM must be unique across every schedule on the terminal. |
8306 | MISSING SCHEDID / SCHED NOT FOUND / INVALID SCHEDID | SCHEDID is missing, doesn't exist on this terminal, or is malformed. |
8307 | MISSING CARD DATA | AC was sent without a TOKEN or card data. |
8308 | PYMT NOT FOUND | No payment on this schedule has that REFNUM. |
8310 | Varies | The payment couldn't be updated or removed. TEXT gives the reason. |
8311 | SCHED CLOSED / SCHED COMPLETE / SCHED SUSPENDED / SCHED CANCELLED | The schedule's status doesn't allow this action. Send GS to check the schedule's status. |
8312 | SCHED NOT READY | PP was sent but the schedule has no card attached. |
8316 | ONLY PLATFEE OR PLATCHRG | A payment has both PLATFEE and PLATCHRG. Send one or the other. |
8317 | MISSING PYMT DATA | PU was sent without both DATE and AMT. |
8319 | PYMT LOCKED | The payment has already been approved, stopped or archived, so it can't be processed, updated or removed. Only Waiting or Declined payments can be changed. |
8320 | PPA ONLY ON PYMTS | PROGRAM, PLAYER or ACCOUNT was sent at the schedule level on CS. Put them on each payment entry in PYMTS instead. |
8399 | SCHED NOT CREATED / SCHED NOT UPDATED | Internal gateway error while saving the schedule. Send GS to check the schedule's actual state before retrying. |
Field Validation
| Code | Message | Description |
|---|---|---|
1031 | INVALID REFNUM | REFNUM isn't 5–40 characters of letters, digits, - and /. |
1032 | Card data error | The card data or token failed validation. TEXT contains the specific message, for example INVALID CARD NUMBER. |
1040 | INVALID FOLLOWUP | FOLLOWUP is longer than 4 characters or contains anything other than letters. |
1052 | INVALID DATE | A payment DATE isn't a valid YYYYMMDD date. |
Amount errors (1011–1013) and PROGRAM / PLAYER / ACCOUNT errors (1011, 8422–8425) are the same as on Direct payments — see Direct Payment Errors. Two rules apply only to schedules:
- A payment
AMTof0.00or less returns1012 AMT TOO LOW, andPLATCHRGcan be at most the lesser of 100.00 and that payment'sAMT. - On
PU,8425also applies when you change theAMTand keep the existing breakdown.
Gateway and Notifications
| Code | Message | Description |
|---|---|---|
9100 | SYSTEM ERROR | Internal gateway error. Retry the request. |
9320 | FAILED / RETRY | A payment notification could not be delivered to your NOTIFICATION URL. |
Updated 1 day ago
Did this page help you?
