Beta version

Welcome to the beta version of the Global Payments 2 API! For the generally available Global Payments API, refer to Global Payments.

Global Payments 2 status responses and error codes

This page contains the status responses and error codes for Global Payments 2.

Status responses

A status response indicates the status of a payment. A sub-status response provides further information about the status of a payment.

The following table contains all the status responses, sub-status responses, and their descriptions for Global Payments 2:

Status responses for Global Payments 2
Status	Sub-status	Description
`RECEIVED`	`RECEIVED`	The payment request was received and will process accordingly.
`ACCEPTED`	`ACCEPTED`	The payment was accepted at the initiation layer.
`PROCESSING`	`PROCESSING BY J.P. MORGAN`	The payment is being processed by J.P. Morgan.
	`PENDING CLIENT REVIEW`	The payment is pending the client's review of fraud-related payment controls.
	`PENDING J.P. MORGAN REVIEW`	The payment is pending an internal review by J.P. Morgan.
	`SCHEDULED`	The payment is scheduled for future execution.
	`SENT TO 'EXTERNAL'`	The payment was sent to an external party, such as a clearinghouse or beneficiary bank.
`CANCELED`	`CANCELED`	The payment was canceled by the client.
`REJECTED`	`REJECTED`	The payment was rejected by J.P. Morgan.
`REJECTED`	`REJECTED BY EXTERNAL`	The payment was rejected by an external party, such as a clearinghouse or beneficiary bank.
`COMPLETED`	`COMPLETED BY J.P. MORGAN`	The payment was fully processed by J.P. Morgan and the necessary movement of money within J.P. Morgan accounts has occurred. It's no longer under the control of J.P. Morgan.
`COMPLETED`	`DELIVERED TO RECIPIENT`	The payment was applied to the receiver's account.
`RETURNED`	`RETURNED`	The payment was returned by an external party, such as a clearinghouse or beneficiary bank.

An error code identifies the reason that a request resulted in an error.

The following tables contain all the possible error codes and their descriptions for Global Payments 2:

Standard API gateway error codes and descriptions
Error code	HTTP code	Rule definition	Description
14000	401	Authentication Failure	Client could not be authenticated
15000	401	System Errors	System Error
10199	403	Signature verification failure	Digital Signature could not be verified. Please re-send the request in a valid format
14000	403	Authorization Failure	Client forbidden from accessing the requested resource
14000	403	Account Authorization Failure	Client not authorized accessing the requested account
15000	403	System Errors	System Error
10107	409	Concurrent request failure	A request with the same Idempotency-Key for the same operation is being processed or is outstanding
10106	422	Idempotency Failure	Idempotency Key must not be reused across different payloads of this operation
10199	422	Invalid Data	Payload could not be decrypted. Please re-send the request in a valid format
12999	503	Service Unavailable	API is currently unavailable for usage. Please try again after some time

The following Card Token Adaptor (CTA) codes are also gateway error codes, but they're only applicable to Push to Card (P2C) Payments:

CTA error codes, HTTP codes, and descriptions
Error code	HTTP code	Description
10001	422	`/payments/debtor/account/alternateAccountIdentifiers/identifier` must be present.
10104	422	`/payments/creditor/account/cardNumber` must have the expected value.
10104	422	`/payments/debtor/account/alternateAccountIdentifiers/identifier` must have the expected value.
13100	422	Suspicious content detected.

400 - Bad request error codes, rule definitions, and descriptions
Error code	Rule definition	Description
10001	Mandatory field missing or invalid	Field `/path/to/field/` must be present Field `/path/to/field/` must be present in the right format
10002	Minimum length violation	Field `/path/to/field/` length must be greater than minimum supported length
10003	Maximum length violation	Field `/path/to/field/` length must be lower than maximum supported length
10100	Minimum value violation	Field `/path/to/field/` value must be greater than minimum supported value
10101	Maximum value violation	Field `/path/to/field/` value must be lower than maximum supported value
10102	Range violation	Field `/path/to/field/` value must be in the expected range
10103	Bad Format	Field `/path/to/field` value must be in the expected format
10104	Bad Value	Field `/path/to/field` value must have the expected value
10105	Unexpected Field	Field `/path/to/field` is not expected in the schema
10199	Other	Will differ depending on nature of error
11001-11499	Business Validation Failures: Account/Permission Problems	Will differ depending on nature of error
11501-11999	Business Validation Failures: General Business Errors	Will differ depending on nature of error
12001-12499	Business Validation Failures: Timeouts	Will differ depending on nature of error
12501-12999	Business Validation Failures: Service Offline	Will differ depending on nature of error
13001-13999	Business Validation Failures: Other Errors	Will differ depending on nature of error