Status and error codes
When Unicorn processes PAIN.001.001.03 and PAIN.008.001.02 input files it creates PAIN.002.001.03 XML output files containing status and error information. Unicorn provides status at the following levels when processing the files received from a customer:
- Group: Header information shown once in the file that is common to all the transactions in that file.
- Batch: A block of either one or more transactions.
- Transaction: A block containing a single transaction.
The Group Header building block in the XML file will show the file-level status in the GrpSts tag as follows:
Status | Meaning |
|---|---|
ACTC | The file was validated and authenticated successfully |
RCVD | The file has been received but is still being validated |
RJCT | The file was rejected |
If a file is rejected, additional information is shown in the StsRsnInf tag. The Cd "NARR" value indicates that there is a reason the file was rejected, with the reason description appearing in the AddtlInf tag as shown in this example:
Here are some examples of reasons that can appear in the Additional information:
- The number of transactions in the file doesn't match the number in the control record.
- The sum of all transactions in the file doesn't match the number in the control record.
- The total in the file exceeds the limit for the customer. In this case, you should contact the CR Client Integration team.
- A validation error was found in the file.
The Batch building block shows batch status as follows:
Status | Meaning |
|---|---|
ACTC | The batch was validated and authenticated successfully |
RCVD | The batch is being checked |
RJCT | The batch was rejected |
PNDG | One or more transactions in the batch is pending |
PART | The transaction batch was partially accepted and partially rejected. This means that the batch includes one or more rejected transactions as well as one or more transactions that have been accepted. In the output file generated by Unicorn, you’ll be able to see which transactions were rejected so you can make the necessary changes and resend to CR. |
If a batch is rejected, additional information is shown in the StsRsnInf tag. The Cd NARR indicates the reason the file was rejected, with the description appearing in the AddtlInf tag. Here are some examples of what might appear in this tag:
- The number of transactions doesn't match the number in the control record.
- The control sums don't correspond with the total calculated.
- The requested execution date is later than the current date and time.
- The creditor's account currency isn't in USD.
- The debtor's account currency isn't in USD.
Statuses at the transaction level can be one of the following:
Status | Meaning |
|---|---|
ACPT | The transaction has been accepted by the external payment processor for processing |
RJCT | The transaction was rejected |
ACSC | The transaction has been completed and the settlement has been confirmed on the debtor's account |
ACSP | The transaction was accepted and has been moved on for processing |
PDNG | The transaction is pending and requires further processing |
If the transaction is rejected, additional information is shown in the StsRsnInf tag. The Cd tag will show either as "NARR" for narrative or "ARET" for a return, with a reason description appearing in the AddtlInf tag. Here are some examples of what might appear in this tag:
- The customer isn't enabled for this rail. In this case, you should contact the CR Client Integration team.
- The account is not set up in Unicorn for this customer. In this case, you should contact the CR Client Integration team.
- In the case of a return, cancellation, or Notice of Change (NOC), a reason code and trace number will be provided here.
- In the case of a wire cancellation, a message will tell you to please contact your RM for more information on this canceled wire.
