Error response codes
Error structure
Errors in Embedded Payments have:
- title: REQUIRED - Short human-readable title for the error.
- httpStatus: OPTIONAL - HTTP Status Code
- traceId: OPTIONAL - J.P. Morgan traced identifier.
- requestId: OPTIONAL - The requestId of your original request.
- context: OPTIONAL (array) - Provides additional context and detail on the validation errors.
- code: OPTIONAL (string) - JPMC Short code that identifies the error - publicly cataloged and documented.
- message: REQUIRED (string) - Humanly readable textual description of the error.
- location: OPTIONAL (string) - either 'body', 'query', or 'path'
- field: OPTIONAL (string) - The location of the property or parameter in error. Where location is 'body' this SHOULD identify the property using a JSONPath representation.
Embedded Payments error code catalog
The following table catalogs the fundamental codes emitted during API request validation:
Embedded Finance Error Code Catalog
The following table catalogs the fundamental codes emitted during API request validation
code | message | iso |
---|---|---|
10001 | Mandatory field missing. | |
10002 | Minimum length violation | |
10003 | Maximum length violation | |
10100 | Minimum value violation | |
10101 | Maximum value violation | |
10102 | Range violation | |
10103 | Bad format | |
10104 | Bad value | |
10105 | Unexpected field | |
11502 | Request-to-pay has already been accepted by the Debtor | ALAC |
11501 | Request-to-pay Expiry Date and Time has already passed | AEXR |
11525 | Request-to-pay has already been refused by the Debtor. | ARFR |
11526 | Request-to-pay has already been rejected | ARJR |
11527 | Attachments to the request-to-pay are not supported. | ATNS |
11201 | Clearing process aborted due to timeout | AB01 |
11101 | Clearing process aborted due to a fatal error | AB02 |
11202 | Settlement aborted due to timeout | AB03 |
11203 | Clearing process aborted due to timeout at the Beneficiary PSP | AB05 |
11205 | Transaction stopped due to timeout at the Instructed Agent | AB06 |
11301 | Agent of message is not online | AB07 |
11302 | Creditor Agent is not online | AB08 |
11102 | Transaction stopped due to error at the Creditor Agent | AB09 |
11103 | Clearing process aborted due to error at the Intermediary PSP or CSM | AB10 |
10204 | Account number is invalid or missing | AC01 |
10205 | Debtor account number invalid or missing | AC02 |
10206 | Creditor account number invalid or missing | AC03 |
11007 | Account number specified has been closed on the bank books | AC04 |
11008 | Debtor account number closed | AC05 |
11009 | Account specified is blocked, prohibiting posting of transactions against it | AC06 |
11010 | Creditor account number closed | AC07 |
10207 | Branch code is invalid or missing | AC08 |
10208 | Account currency is invalid or missing | AC09 |
10209 | Debtor account currency is invalid or missing | AC10 |
10210 | Creditor account currency is invalid or missing | AC11 |
10211 | Account type missing or invalid | AC12 |
10212 | Debtor account type missing or invalid | AC13 |
10213 | Creditor account type missing or invalid | AC14 |
11015 | The account details for the counterparty have changed | AC15 |
11016 | Credit or debit card number is invalid | AC16 |
11011 | Transaction forbidden on this type of account (formerly No Agreement) | AG01 |
10214 | Bank Operation code specified in the message is not valid for receiver | AG02 |
11012 | Transaction type not supported or authorized on this account | AG03 |
10215 | Agent country code is missing or invalid | AG04 |
11021 | Debtor agent country code is missing or invalid | AG05 |
11022 | Creditor agent country code is missing or invalid | AG06 |
11104 | Debtor account cannot be debited for a generic reason | AG07 |
11401 | Transaction failed due to invalid or missing user or access right | AG08 |
11013 | Original payment never received | AG09 |
11014 | Agent of message is suspended from the Real Time Payment system | AG10 |
11015 | Beneficiary PSP of message is suspended from the Real Time Payment system | AG11 |
11105 | Pre-Authorization Validation Failed | AG12 |
11029 | Returned payments derived from previously returned transactions are not allowed | AG13 |
11030 | Agent in the payment workflow is incorrect | AGNT |
10216 | Specified message amount is equal to zero | AM01 |
11106 | Specific transaction or message amount is greater than allowed maximum | AM02 |
11107 | Specified message amount is an non processable currency outside of existing agreement | AM03 |
11016 | Amount of funds available to cover specified message amount is insufficient | AM04 |
11108 | Duplication | AM05 |
10217 | Specified transaction amount is less than agreed minimum | AM06 |
11509 | Amount specified in message has been blocked by regulatory authorities. | AM07 |
11109 | Amount received is not the amount agreed or expected | AM09 |
11511 | Sum of instructed amounts does not equal the control sum | AM10 |
10218 | Transaction currency is invalid or missing | AM11 |
10219 | Amount is invalid or missing | AM12 |
11017 | Transaction amount exceeds limits set by clearing system | AM13 |
11018 | Transaction amount exceeds limits agreed between bank and client | AM14 |
11019 | Transaction amount below minimum set by clearing system | AM15 |
11517 | Control Sum at the Group level is invalid | AM16 |
11518 | Control Sum at the Payment Information level is invalid | AM17 |
11519 | Number of transactions is invalid or missing | AM18 |
11520 | Number of transactions at the Group level is invalid or missing | AM19 |
11521 | Number of transactions at the Payment Information level is invalid | AM20 |
11018 | Transaction amount exceeds limits agreed between bank and client | AM21 |
11523 | Unable to apply zero amount to designated account | AM22 |
11020 | Transaction amount exceeds settlement limit | AM23 |
11031 | Identification of end customer is not consistent with associated account number | BE01 |
10220 | Missing Creditor Address | BE04 |
11033 | Party who initiated the message is not recognised by the end customer | BE05 |
11111 | End customer specified is not known at Sort or National Bank Code or does no longer exist in books | BE06 |
11528 | Specification of debtor's address, which is required for payment, is missing/not correct | BE07 |
10221 | Debtor name is missing | BE08 |
10222 | Country code is missing or Invalid | BE09 |
10223 | Creditor country code is missing or invalid | BE11 |
11533 | Country code of residence is missing or Invalid | BE12 |
11534 | Country code of debtor's residence is missing or Invalid | BE13 |
11535 | Country code of creditor's residence is missing or Invalid | BE14 |
11534 | Country code of debtor's residence is missing or Invalid | BE15 |
10224 | Debtor or Ultimate Debtor identification code missing or invalid | BE16 |
10226 | Creditor or Ultimate Creditor identification code missing or invalid | BE17 |
10227 | Contact details missing or invalid | BE18 |
11540 | Charge bearer code for transaction type is invalid | BE19 |
11541 | Name length exceeds local rules for payment type. | BE20 |
10228 | Name missing or invalid | BE21 |
10229 | Creditor name is missing | BE22 |
11544 | Phone number or email address, or any other proxy, used as the account proxy is unknown or invalid | BE23 |
11545 | Credit transfer is not tagged as an Extended Remittance Information (ERI) transaction but contains ERI. | CERI |
10230 | Value in Requested Execution Date or Requested Collection Date is too far in the future | CH03 |
10231 | Value in Requested Execution Date or Requested Collection Date is too far in the past | CH04 |
11548 | Element is not to be used at B- and C-Level | CH07 |
11021 | Mandate changes are not allowed | CH09 |
11549 | Information on mandate changes are missing | CH10 |
11112 | Value in Creditor Identifier is incorrect | CH11 |
11551 | Value in Creditor Identifier is incorrect | CH12 |
11552 | Original Debtor Account is not to be used | CH13 |
11553 | Original Debtor Agent is not to be used | CH14 |
10232 | Content Remittance Information/Structured includes more than 140 characters | CH15 |
11555 | Content is incorrect | CH16 |
11556 | Element is not allowed | CH17 |
11557 | Values in Interbank Settlement Date or Requested Collection Date will be set to the next TARGET day | CH19 |
11558 | Number of decimal points not compatible with the currency | CH20 |
10233 | Mandatory element is missing | CH21 |
11560 | SDD CORE and B2B not permitted within one message | CH22 |
11561 | Cheque has been presented in cheque clearing and settled on the creditor’s account. | CHQC |
11113 | Creditor bank is not registered under this BIC in the CSM | CNOR |
11562 | Authorisation is cancelled | CN01 |
11114 | Cancellation requested by the Debtor | CUST |
11564 | Currency of the payment is incorrect | CURR |
11566 | Rejection of a payment due to covering FI settlement not being received | DC02 |
11115 | Debtor bank is not registered under this BIC in the CSM | DNOR |
11036 | Data signature is required | DS0A |
11037 | Data signature for the format is not available or invalid. | DS0B |
11038 | The signer certificate is revoked | DS0C |
11039 | The signer certificate is not valid (revoked or not active) | DS0D |
11040 | The signer certificate is not present | DS0E |
11041 | The authority of the signer certification sending the certificate is unknown | DS0F |
11042 | Signer is not allowed to sign this operation type | DS0G |
11044 | The number of transaction is over the number allowed for this signer | DS0H |
11036 | Data signature is required | DS0K |
11568 | The electronic signature(s) is/are correct | DS01 |
11116 | Order Cancelled | DS02 |
11570 | The user’s attempt to cancel the order was not successful | DS03 |
11117 | Order Rejected | DS04 |
11572 | The order was correct and could be forwarded for postprocessing | DS05 |
11573 | The order was transferred to VEU | DS06 |
11574 | The decompression of the file was not successful | DS08 |
11118 | The decryption of the file was not successful | DS09 |
11045 | The certificate is revoked for the first signer | DS10 |
11046 | The certificate is not valid (revoked or not active) for the first signer | DS11 |
11047 | The certificate is not present for the first signer | DS12 |
11048 | The authority of signer certification sending the certificate is unknown for the first signer | DS13 |
11049 | The user is unknown on the server | DS14 |
11050 | The same signature has already been sent to the bank | DS15 |
11051 | The public key version is not correct | DS16 |
11052 | Order data and signatures don’t match | DS17 |
11053 | File cannot be tested, the complete order has to be repeated | DS18 |
11054 | The user’s rights (concerning his signature) are insufficient to execute the order | DS19 |
11055 | The certificate is revoked for the second signer | DS20 |
11056 | The certificate is not valid (revoked or not active) for the second signer | DS21 |
11057 | The certificate is not present for the second signer | DS22 |
11058 | The authority of signer certification sending the certificate is unknown for the second signer | DS23 |
11059 | Waiting time expired due to incomplete order | DS24 |
11060 | The order file was deleted by the bank server (for multiple reasons) | DS25 |
11061 | The same user has signed multiple times | DS26 |
11062 | The user is not yet activated (technically) | DS27 |
10234 | Invalid date (eg, wrong or missing settlement date) | DT01 |
11577 | Invalid creation date and time in Group Header (eg, historic date) | DT02 |
11578 | Invalid non bank processing date (eg, weekend or local public holiday) | DT03 |
10235 | Future date not supported | DT04 |
11580 | Associated message, payment information block or transaction was received after agreed processing cut-off date, i.e., date in the past | DT05 |
11581 | Execution Date has been modified in order for transaction to be processed | DT06 |
11582 | Message Identification is not unique | DU01 |
11583 | Payment Information Block is not unique | DU02 |
11121 | Transaction is not unique | DU03 |
11585 | End To End ID is not unique | DU04 |
11122 | Instruction ID is not unique | DU05 |
11123 | Payment is a duplicate of another payment | DUPL |
11124 | Creditor Agent BIC and IBAN Mismatch | EC10 |
11023 | Sanctions Reject | EC46 |
11125 | Settlement of the transaction has failed | ED05 |
11303 | Interbank settlement system not available | ED06 |
11126 | File Format incomplete or invalid | FF01 |
10236 | Payment Type Information is missing or invalid | FF03 |
10237 | Service Level code is missing or invalid | FF04 |
10238 | Category Purpose code is missing or invalid | FF06 |
10239 | Purpose is missing or invalid | FF07 |
10240 | End to End Id missing or invalid | FF08 |
11127 | File or transaction cannot be processed due to technical issues at the bank side | FF10 |
11128 | Clearing request rejected due it being subject to an abort operation | FF11 |
11129 | Following Cancellation Request | FOCR |
11024 | Returned as a result of fraud | FR01 |
11130 | Fraudulent Original SCT Inst Transaction | FRAD |
11121 | The Status Originator performed the account booking and transferred the cover transaction to the next Reimbursement Agent or to a Market Infrastructure. The payment transfer is tracked. No further updates will follow from the Status Originator. | G000 |
11122 | The Status Originator performed the account booking and transferred the cover transaction to the next Reimbursement Agent or to a Market Infrastructure. The payment transfer is not tracked. No further updates will follow from the Status Originator. | G001 |
11123 | Debit/credit to nostro account may not be confirmed same day or Financial Institution Credit Transfer may not be transferred same day. Update will follow from the Status Originator. | G002 |
11124 | Status Originator has requested a previous Agent to provide additional information/correct information. Update will follow from the Status Originator. | G003 |
11125 | Credit to the creditor’s account is pending, status Originator is waiting for funds provided via a cover. Update will follow from the Status Originator. | G004 |
11126 | Payment has been delivered to creditor agent with service level | G005 |
11127 | Payment has been delivered to creditor agent without service level | G006 |
11131 | Legal Decision | LEGL |
11132 | No Mandate | MD01 |
11133 | Mandate related information data required by the scheme is missing | MD02 |
11065 | Creditor or creditor's agent should not have collected the direct debit | MD05 |
11134 | Return of funds requested by end customer | MD06 |
11135 | End customer is deceased | MD07 |
11136 | Not Specified Reason Customer Generated | MS02 |
11137 | Reason has not been specified by agent | MS03 |
11401 | Generic clearing error | NARR |
11068 | No existing agreement for receiving request-to-pay messages | NOAR |
11138 | No response from Beneficiary | NOAS |
11070 | Customer account is not compliant with regulatory requirements | NOCM |
11071 | Requested payment guarantee (by Creditor) related to a request-to-pay cannot be provided | NOPG |
11139 | Initial SCT Inst Transaction never received | NOOR |
11072 | Recipient side of the request-to-pay (payer or its request-to-pay service provider) is not reachable | NRCH |
11073 | Type of payment requested in the request-to-pay is not supported by the payer | PINS |
10241 | Proxy Id Invalid or missing | PR01 |
10243 | No iso code but has system code match | PR02 |
10244 | Proxy ID missing | PR03 |
10245 | Proxy Type missing | PR04 |
11140 | Duplicate Proxy in Bank | PR05 |
11141 | Duplicate Proxy in another Bank | PR06 |
11142 | Proxy already registered/ transferred | PR07 |
11143 | Proxy already deregistered | PR08 |
11144 | Proxy already suspended | PR09 |
11207 | Proxy request timeout | PR10 |
11145 | Proxy Other rejection reason | PR11 |
11146 | Proxy ID Not Active | PR12 |
10246 | Unknown BIC in routing table | PY01 |
11147 | QR Status Inactive | QR01 |
11148 | QR Code Expired | QR02 |
11128 | Request-to-pay has been received and can be processed further | REPR |
10247 | Bank identifier code specified in the message has an incorrect format | RC01 |
10248 | Bank identifier is invalid or missing | RC02 |
10249 | Debtor bank identifier is invalid or missing | RC03 |
10250 | Creditor bank identifier is invalid or missing | RC04 |
10251 | BIC identifier is invalid or missing | RC05 |
11621 | Debtor BIC identifier is invalid or missing | RC06 |
11622 | Creditor BIC identifier is invalid or missing | RC07 |
11623 | Invalid ACH Routing Number | RC08 |
10252 | Debtor ClearingSystemMember identifier is invalid or missing | RC09 |
10253 | Creditor ClearingSystemMember identifier is invalid or missing | RC10 |
11149 | Transaction reference is not unique within the message | RF01 |
10254 | Specification of the debtor account or unique identification is insufficient or missing | RR01 |
10255 | Specification of the debtor name, address is insufficient or missing | RR02 |
10256 | Missing Creditors Name or Address | RR03 |
11150 | Regulatory Reason | RR04 |
10257 | Regulatory or Central Bank Reporting information missing, incomplete or invalid | RR05 |
10258 | Tax information missing, incomplete or invalid | RR06 |
10259 | Remittance information structure does not comply with rules for payment type | RR07 |
10260 | Structured creditor reference invalid or missing | RR09 |
11129 | Return following investigation request and no remediation possible | RUTA |
11130 | Request for Cancellation is acknowledged following validation | S000 |
11131 | Unique End-to-end Transaction Reference (UETR) relating to a payment has been identified as being associated with a Request for Cancellation | S001 |
11132 | Unique End-to-end Transaction Reference (UETR) relating to a payment has been prevent from traveling across a messaging network | S002 |
11133 | Request for Cancellation has been forwarded to the payment processing/last payment processing agent | S003 |
11134 | Request for Cancellation has been acknowledged as delivered to payment processing/last payment processing agent | S004 |
11151 | Due to a specific service offered by the clearing system | SL03 |
11074 | Whitelisting service offered by the Debtor Agent; Debtor has not included the Creditor on its “Whitelist” (yet). In the Whitelist the Debtor may list all allowed Creditors to debit Debtor bank account | SL11 |
11075 | Blacklisting service offered by the Debtor Agent; Debtor included the Creditor on his “Blacklist”. In the Blacklist the Debtor may list all Creditors not allowed to debit Debtor bank account | SL12 |
11076 | Due to Maximum allowed Direct Debit Transactions per period service offered by the Debtor Agent | SL13 |
11077 | Due to Maximum allowed Direct Debit Transaction amount service offered by the Debtor Agent | SL14 |
11152 | The transmission of the file was not successful – it had to be aborted (for technical reasons) | TA01 |
11135 | The (technical) transmission of the file was successful | TS01 |
11136 | The order was transferred to pass by accompanying note signed by hand | TS04 |
11153 | Technical Problem | TECH |
11078 | Unknown Creditor | UCRD |
11079 | Payment is not justified | UPAY |
10261 | Invalid IBAN format | XD19 |
11154 | Insufficient liquidity for processing the transaction on the System. | XT04 |
11155 | Invalid Accept Time, Rejected by the CSM to Originator Bank upon exceeding tolerance period for the Acceptance Date&Time | XT06 |
11156 | Unsupported XML field | XT13 |
11157 | Invalid data format | XT33 |
10262 | Invalid country code | XT73 |
11158 | Invalid original transaction status, action not required | XT75 |
11159 | Original Amount mismatch | XT77 |
11025 | The Debtor Agent is not allowed to send SCT Inst transactions (pacs.008) and consequently to send Payment Status Request (pacs.028) and Recalls (camt.056). It is also not allowed to receive NRR and PRR. | XT79 |
11026 | The Creditor Agent is not allowed to receive SCT Inst transactions (pacs.008) and consequently to receive Payment Status request (pacs.028) and Recalls (camt.056). It is also not allowed to send NRR and PRR | XT80 |
11027 | Field not Permitted in SCT Inst Service | XT81 |
11160 | Sender and/or Receiver Participants not configured for CUG/AOS usage | XT83 |
11161 | Inconsistent Instructing Agents | XT87 |
11162 | Invalid use of a Technical BIC | XT90 |
GCA errors
You may occassionally get error messages from our API gateway. They have a slightly different structure to other synchronous error responses.
GCA Code |
Http Status |
Message |
GCA-001 |
403 |
Unauthorized Access |
GCA-003 |
403 |
Unauthorized Access |
GCA-099 |
500 |
System is Unavailable (timeout issue or downstream system is unavailable) |
Error payload examples
Take a look at these error message examples to better understand the structure and form of error messages.
Synchronous API response example
Synchronous API error example
Json
HTTP/1.1 400
Content-Type: application/json
{
"title" : "Invalid Data",
"httpStatus" : 400,
"traceId" : "xxxxx-yyyyyy-zzzzzz",
"context" : [
{
"code": "10001"
"message": "Property 'amount' must be present",
"field": "amount",
"location": "body"
},
{
"code": "10100"
"message": "'pagesize' must be greater than 10",
"field": "pageSize",
"location": "query"
},
{
"code": "10102"
"message": "'toDate must be later than 'fromDate'",
"location": "query"
},
{
"code": "10104",
"message": "XZY is not a valid currency code",
"location": "body",
"field": "$.amount.currencyCode"
}
]
}
Synchronous API response with GCA error structure
Example of gateway error message structure
Json
{
"errors": [
{
"errorCode": "GCA-099",
"errorMsg": "System is Unavailable"
}
]
}
Webhook (asycnhronous) error example
Json
Content-Type: application/json
{
"eventType": "TRANSACTIONS_FAILED",
"resourceType": "TRANSACTIONS",
"resourceId": "123456789",
"resource": {
"creditorAccount": "9414-3568-5326967",
"debtorAccount": "9fur8fmgndkd",
"amount": 1.245,
"transactionReferenceId": "inv-pay-123"
},
"errors": {
"title" : "Invalid Data",
"httpStatus" : 400,
"traceId" : "xxxxx-yyyyyy-zzzzzz",
"context" : [
{
"code": "10001"
"message": "Property 'amount' must be present",
"field": "amount",
"location", "body"
},
{
"code": "10100"
"message": "'pagesize' must be greater than 10",
"field": "pageSize",
"location", "query"
},
{
"code": "10102"
"message": "'toDate must be later than 'fromDate'",
"location": "query"
},
{
"code": "10104",
"message": "XZY is not a valid currency code",
"location": "body",
"field": "$.amount.currencyCode"
}
]
}
}