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

CodeMessageDescription
8300INVALID SUBTYPE / request format errorThe SUBTYPE isn't a schedule action, or the request couldn't be read. TEXT describes the problem.
8301DUPLICATE SCHEDIDA schedule with this SCHEDID already exists on this terminal.
8302MISSING INVOICEINVOICE was not sent on CS.
8303VariesThe payment couldn't be added to the schedule. TEXT gives the reason.
8304INVALID PYMT DATE / INVALID DATE / MISSING REFNUMA 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.
8305DUPLICATE REFNUMA payment with this REFNUM already exists on this terminal. REFNUM must be unique across every schedule on the terminal.
8306MISSING SCHEDID / SCHED NOT FOUND / INVALID SCHEDIDSCHEDID is missing, doesn't exist on this terminal, or is malformed.
8307MISSING CARD DATAAC was sent without a TOKEN or card data.
8308PYMT NOT FOUNDNo payment on this schedule has that REFNUM.
8310VariesThe payment couldn't be updated or removed. TEXT gives the reason.
8311SCHED CLOSED / SCHED COMPLETE / SCHED SUSPENDED / SCHED CANCELLEDThe schedule's status doesn't allow this action. Send GS to check the schedule's status.
8312SCHED NOT READYPP was sent but the schedule has no card attached.
8316ONLY PLATFEE OR PLATCHRGA payment has both PLATFEE and PLATCHRG. Send one or the other.
8317MISSING PYMT DATAPU was sent without both DATE and AMT.
8319PYMT LOCKEDThe 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.
8320PPA ONLY ON PYMTSPROGRAM, PLAYER or ACCOUNT was sent at the schedule level on CS. Put them on each payment entry in PYMTS instead.
8399SCHED NOT CREATED / SCHED NOT UPDATEDInternal gateway error while saving the schedule. Send GS to check the schedule's actual state before retrying.

Field Validation

CodeMessageDescription
1031INVALID REFNUMREFNUM isn't 5–40 characters of letters, digits, - and /.
1032Card data errorThe card data or token failed validation. TEXT contains the specific message, for example INVALID CARD NUMBER.
1040INVALID FOLLOWUPFOLLOWUP is longer than 4 characters or contains anything other than letters.
1052INVALID DATEA 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 AMT of 0.00 or less returns 1012 AMT TOO LOW, and PLATCHRG can be at most the lesser of 100.00 and that payment's AMT.
  • On PU, 8425 also applies when you change the AMT and keep the existing breakdown.

Gateway and Notifications

CodeMessageDescription
9100SYSTEM ERRORInternal gateway error. Retry the request.
9320FAILED / RETRYA payment notification could not be delivered to your NOTIFICATION URL.

Did this page help you?