pacs.002
Currently the Icon Standard for pacs.002 messages only applies to those received from a CSM.
In the future it will also support sending `pacs.002`s to the scheme.
|
When using the Icon Standard, the only modification to a pacs.002 message affects the response codes returned to the client — whether the response originates from a payment scheme or from the SCT Validation API.
To simplify response processing, all proprietary return codes are automatically mapped to Icon Standard Reason Codes. This eliminates the need for clients to manage or interpret scheme-specific codes across different implementations.
The original proprietary code is not lost — it is included in the accompanying business data section of the pacs.002 message for reference.
RT1
IPF Code |
RT1 Code |
Reason Description |
IPFCSM001 |
AC03 |
Wrong IBAN |
IPFCSM010 |
B00 |
Bulk Accepted |
IPFCSM013 |
B03 |
Number of transactions mismatch |
IPFCSM014 |
B05 |
Total amount mismatch |
IPFCSM016 |
B09 |
Bulk rejected due to the rejection of the related transaction |
IPFCSM017 |
B10 |
Instructing Agent mismatch or not valid |
IPFCSM018 |
B11 |
Invalid use of Instructed Agent |
IPFCSM022 |
B15 |
Invalid Settlement Date |
IPFCSM023 |
B16 |
Invalid Settlement Info details |
IPFCSM050 |
E001 |
Duplication in identity ID is not allowed |
IPFCSM051 |
E002 |
Overlap of un-availability periods not allowed for same BIC |
IPFCSM052 |
E003 |
Unknown BIC |
IPFCSM053 |
E004 |
Wrong Time |
IPFCSM054 |
E005 |
Un-availability too far |
IPFCSM055 |
E006 |
Daily threshold passed |
IPFCSM056 |
E007 |
No matching available |
IPFCSM057 |
E008 |
Cancel not allowed in the past |
IPFCSM058 |
E009 |
Invalid value |
IPFCSM100 |
L001 |
Unknown Creditor or Creditor Account |
IPFCSM101 |
L002 |
Unknown Debtor or Debtor Account |
IPFCSM102 |
L003 |
Currency of incoming flow differs from Account currency or RTGS System not configured |
IPFCSM103 |
L004 |
The Creditor or the Creditor Account is blocked |
IPFCSM104 |
L005 |
The Debtor or the Debtor Account is blocked |
IPFCSM105 |
L006 |
Outbound or Inbound LT is a duplicate submission |
IPFCSM106 |
L007 |
Failure of the settlement attempt of the instruction due to insufficient cash balance |
IPFCSM107 |
L008 |
RTGS system is closed |
IPFCSM108 |
L009 |
Invalid content of the field RTGS Status |
IPFCSM109 |
L010 |
Unknown RTGS System DN |
IPFCSM110 |
L011 |
Order not found |
IPFCSM111 |
L012 |
The amount is lower or equal to zero |
IPFCSM113 |
L014 |
Intra-service LT not allowed |
IPFCSM150 |
PY01 |
Unknown BIC in routing table |
IPFCSM151 |
PY03 |
Unknown BIC in TIPS Directory |
IPFCSM160 |
R001 |
Restriction Type for Actor not allowed |
IPFCSM161 |
R002 |
Party not existing |
IPFCSM162 |
R003 |
Party Type not allowed for blocking/unblocking operations |
IPFCSM163 |
R005 |
Restriction Type for account/CMB not allowed |
IPFCSM164 |
R006 |
Account/CMB not existing |
IPFCSM165 |
R007 |
Currency not correct |
IPFCSM166 |
R008 |
User not allowed to block/unblock the account/CMB |
IPFCSM167 |
R020 |
CMB not existing |
IPFCSM168 |
R021 |
User not allowed to change the Limit |
IPFCSM169 |
R099 |
Duplicate instruction |
IPFCSM200 |
S001 |
Request not allowed |
IPFCSM201 |
S002 |
Data not available |
IPFCSM252 |
TECH |
Technical Problem |
IPFCSM400 |
XD19 |
Invalid IBAN format |
IPFCSM401 |
XD20 |
Invalid Account Number |
IPFCSM402 |
XD21 |
Invalid Account Owner |
IPFCSM403 |
XD22 |
Invalid settlement method for either Debtor Agent or Creditor Agent |
IPFCSM421 |
XT01 |
RT1 System unavailable |
IPFCSM422 |
XT04 |
Insufficient liquidity for processing the transaction on the System. |
IPFCSM424 |
XT06 |
Invalid AccptTime Rejected by the CSM to Originator PSP upon exceeding tolerance period for the Acceptance Date&Time |
IPFCSM425 |
XT10 |
Transaction inflight |
IPFCSM426 |
XT13 |
Unsupported XML field |
IPFCSM427 |
XT33 |
Invalid data format |
IPFCSM431 |
XT73 |
Invalid country code |
IPFCSM433 |
XT75 |
Invalid original transaction status action not required |
IPFCSM434 |
XT77 |
Original Amount mismatch |
IPFCSM435 |
XT79 |
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. The sender Participant is not allowed to send liquidity transfer order |
IPFCSM436 |
XT80 |
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.(The a admission profile “Debtor Only” currently is not implemented) |
IPFCSM437 |
XT81 |
Field not Permitted in SCT Inst Service |
IPFCSM438 |
XT83 |
Sender and/or Receiver Participants not configured for CUG/AOS usage |
IPFCSM440 |
XT87 |
Inconsistent Instructing Agent |
IPFCSM441 |
XT90 |
Invalid use of a Technical BIC |
IPFCSM999 |
Unmapped Error |
SCT
IPF Code |
SCT Code |
Reason Description |
IPFCSM002 |
A00 |
Input file entirely valid |
IPFCSM003 |
A01 |
Input file partially valid |
IPFCSM010 |
B00 |
Bulk Accepted |
IPFCSM011 |
B01 |
Bulk/batch partially valid |
IPFCSM012 |
B02 |
Maximum Size of a Batch Exceeded |
IPFCSM013 |
B03 |
Number of transactions mismatch |
IPFCSM014 |
B05 |
Total amount mismatch |
IPFCSM015 |
B08 |
Maximum number of bulks/batches in a file exceeded |
IPFCSM016 |
B09 |
Bulk rejected due to the rejection of the related transaction |
IPFCSM017 |
B10 |
Instructing Agent mismatch or not valid |
IPFCSM018 |
B11 |
Invalid use of Instructed Agent |
IPFCSM019 |
B12 |
Invalid Use of Assgnr/Assgne |
IPFCSM020 |
B13 |
Zero Settlement Amount |
IPFCSM021 |
B14 |
Duplicate MessageID |
IPFCSM022 |
B15 |
Invalid Settlement Date |
IPFCSM023 |
B16 |
Invalid Settlement Info details |
IPFCSM024 |
B17 |
Invalid LAC |
IPFCSM025 |
B23 |
Too many consecutive rejected transactions |
IPFCSM026 |
B24 |
Invalid use of bulk/batch transaction |
IPFCSM027 |
B25 |
Instructing or Instructed Agent not Allowed to Use Batch Processing Option |
IPFCSM028 |
B30 |
DPWS Bulk/Batch Cancellation Rejected |
IPFCSM150 |
PY01 |
Unknown BIC in routing table |
IPFCSM253 |
BFUP |
Before the Update of the Participant Position |
IPFCSM254 |
CANC |
Used in PCF file The PCR was processed before the beginning of the settlement process of the original Credit Transfer. The original CT was not settled. |
IPFCSM255 |
ED05 |
Settlement Failed |
IPFCSM256 |
FTUP |
After the Update of the Participant Position |
IPFCSM257 |
LTIN |
Liquidity Transfer Instructions |
IPFCSM258 |
PCR |
Value always set for PCF file |
IPFCSM259 |
PLCR |
Processed LCRs |
IPFCSM260 |
PROC |
Processed |
IPFCSM300 |
R01 |
IGF received on non-Target day |
IPFCSM301 |
R02 |
Network file name not compliant |
IPFCSM302 |
R03 |
Unknown Service identifier |
IPFCSM303 |
R04 |
Direct Participant BIC mismatch (network address) |
IPFCSM304 |
R06 |
Invalid file name format |
IPFCSM305 |
R07 |
Invalid file extension |
IPFCSM306 |
R08 |
Unable to process input file/file too big |
IPFCSM307 |
R10 |
Schema validation failed |
IPFCSM308 |
R11 |
Invalid Sending Institution |
IPFCSM309 |
R12 |
Invalid Receiving Institution |
IPFCSM310 |
R13 |
Duplicate ICF/IQF/IGF |
IPFCSM311 |
R14 |
Invalid Test Code |
IPFCSM312 |
R15 |
Invalid Sending Institution BIC format |
IPFCSM313 |
R16 |
Invalid Receiving Institution BIC format |
IPFCSM314 |
R17 |
Invalid Service Identifier in File Header |
IPFCSM315 |
R18 |
Credit Transfer bulk/batch number mismatch |
IPFCSM316 |
R19 |
Payment Cancellation Request bulk/batch number mismatch |
IPFCSM317 |
R20 |
Returns bulk/batch number mismatch |
IPFCSM318 |
R21 |
Resolution of Investigation bulk/batch number mismatch |
IPFCSM319 |
R23 |
All bulks/batches rejected |
IPFCSM320 |
R24 |
Maximum number of input files received |
IPFCSM321 |
R25 |
Payment Status Request bulk number mismatch |
IPFCSM322 |
R26 |
Claim Not-Receipt bulk number mismatch |
IPFCSM323 |
R27 |
Request to Modify Payment bulk number mismatch |
IPFCSM324 |
R28 |
Resolution of Investigation (V09) bulk number mismatch |
IPFCSM325 |
R30 |
Sending Direct Participant not Enabled for Batch Processing Option |
IPFCSM326 |
R31 |
Get Account bulk number mismatch |
IPFCSM327 |
R32 |
Get Transaction bulk number mismatch |
IPFCSM350 |
RCLL |
The PCR was processed after the settlement of the original Credit Transfer. The CT has been settled/cancelled by the ESM and the Recall Request was forwarded to the Beneficiary PSP of the original CT. |
IPFCSM351 |
RJCT |
The transfer of money has been rejected. |
IPFCSM352 |
RVKD |
The transfer of money has been revoked by the Participant via GUI or API. |
IPFCSM400 |
XD19 |
Invalid IBAN format |
IPFCSM420 |
XT00 |
Transaction included in Settled LCR The transaction has been settled in CGS |
IPFCSM423 |
XT05 |
Transaction queued in CGS The transaction is queued in CGS. |
IPFCSM426 |
XT13 |
Unsupported XML field |
IPFCSM427 |
XT33 |
Invalid data format |
IPFCSM428 |
XT44 |
If the LCR has not closed its life cycle thus the relevant status is equal to PENDING in CGS or WAITING in S2 Service the Sender DP must not be equal to the DP BIC configured for the Credit Party Settlement BIC stored for the relevant LCR. |
IPFCSM429 |
XT45 |
No matching found The LCR reference is not found in STEP2 repositories |
IPFCSM430 |
XT46 |
No Queued LCRs in CGS |
IPFCSM431 |
XT73 |
Invalid country code |
IPFCSM432 |
XT74 |
Invalid Original Transaction Status Action Required Invalid original transaction status for R-message received action required. |
IPFCSM433 |
XT75 |
Invalid original transaction status action not required |
IPFCSM434 |
XT77 |
Original Amount mismatch |
IPFCSM437 |
XT81 |
Field not Permitted in SCT Inst Service |
IPFCSM439 |
XT86 |
Expired Time Limit for PCR Payment Cancellation Request rejected due to expired time limit for Credit Transfer cancellation (not valid for Request For Recall by the Originator). |
IPFCSM440 |
XT87 |
Inconsistent Instructing Agent |
IPFCSM441 |
XT90 |
Invalid use of a Technical BIC |
IPFCSM442 |
XT91 |
Not Allowed in SEPACOM Creditor Agent or Debtor Agent of the original transaction is not allowed to be part of the SEPACOM Closed User Group |
IPFCSM443 |
XT92 |
Instructed Agent not allowed for Non-Target Day AOS The instructed agent resulting from the look-up for this transaction is not configured for Non-Target day settlement |
IPFCSM999 |
Unmapped Error |
TIPS
IPF Code |
TIPS Code |
Reason Description |
IPFCSM100 |
L001 |
Unknown Creditor or Creditor Account |
IPFCSM101 |
L002 |
Unknown Debtor or Debtor Account |
IPFCSM102 |
L003 |
Currency of incoming flow differs from Account currency or RTGS System not configured |
IPFCSM103 |
L004 |
The Creditor or the Creditor Account is blocked |
IPFCSM104 |
L005 |
The Debtor or the Debtor Account is blocked |
IPFCSM105 |
L006 |
Outbound or Inbound LT is a duplicate submission |
IPFCSM106 |
L007 |
Failure of the settlement attempt of the instruction due to insufficient cash balance |
IPFCSM107 |
L008 |
RTGS system is closed |
IPFCSM108 |
L009 |
Invalid content of the field RTGS Status |
IPFCSM109 |
L010 |
Unknown RTGS System DN |
IPFCSM110 |
L011 |
Order not found |
IPFCSM111 |
L012 |
The amount is lower or equal to zero |
IPFCSM112 |
L013 |
LT via a transit account is allowed in contingency scenario only |
IPFCSM113 |
L014 |
Intra-service LT not allowed |
IPFCSM114 |
L015 |
User not authorised when the RTGS System is partially closed |
IPFCSM115 |
L099 |
Cannot determine the direction of the LT order |
IPFCSM160 |
R001 |
Restriction Type for Actor not allowed |
IPFCSM161 |
R002 |
Party not existing |
IPFCSM162 |
R003 |
Party Type not allowed for blocking/unblocking operations |
IPFCSM163 |
R005 |
Restriction Type for account/CMB not allowed |
IPFCSM164 |
R006 |
Account/CMB not existing |
IPFCSM165 |
R007 |
Currency not correct |
IPFCSM166 |
R008 |
User not allowed to block/unblock the account/CMB |
IPFCSM167 |
R020 |
CMB not existing |
IPFCSM168 |
R021 |
User not allowed to change the Limit |
IPFCSM169 |
R099 |
Duplicate instruction |
IPFCSM200 |
S001 |
Request not allowed |
IPFCSM201 |
S002 |
Data not available |
IPFCSM250 |
TBL1 |
The owner of the debtor account or the debtor account/CMB is blocked |
IPFCSM251 |
TBL2 |
The owner of the creditor account or the creditor account/CMB is blocked |
IPFCSM999 |
Unmapped Error |
SIC
IPF Code |
SIC Code |
Reason Description |
IPFCSM014 |
129 |
Total amount mismatch |
IPFCSM052 |
102 |
Unknown BIC |
IPFCSM427 |
103, 112 |
Invalid data format |
IPFCSM437 |
105 |
Field not Permitted in SCT Inst Service |
IPFCSM500 |
108 |
Date too far in the past |
IPFCSM501 |
127 |
Incorrect check digit |
IPFCSM502 |
134 |
Incorrect authenticator |
IPFCSM503 |
137 |
Field dependency error |
IPFCSM504 |
142 |
Message not possible at current clearing status |
IPFCSM505 |
166 |
Account not stopped |
IPFCSM506 |
168 |
Rule regarding special characters in transaction reference violated |
IPFCSM507 |
207 |
Number of transactions must be 1 |
IPFCSM508 |
208 |
Settlement method must be CLRG |
IPFCSM509 |
209 |
Unknown participant identification |
IPFCSM510 |
210 |
Field occurs too often |
IPFCSM511 |
212 |
Maximum length of all contents of sub-elements of this element exceeded |
IPFCSM512 |
219 |
Pre-value date not permitted |
IPFCSM513 |
220 |
QR-IBAN/QR-IID not permitted |
IPFCSM514 |
223 |
" Full address option requires mandatory ""Nm"" and ""PstlAdr""" |
IPFCSM515 |
224 |
Element requires additional sub-elements |
IPFCSM516 |
225 |
" Simultaneous use of structured and unstructured address information is not allowed for the ""PstlAdr"" element" |
IPFCSM517 |
226 |
Account balance not covered |
IPFCSM518 |
227 |
Start time is too far in the future |
IPFCSM519 |
228 |
SIC IP acceptance time out exceeded |
IPFCSM520 |
229 |
IP defence limit amount exceeded |
IPFCSM521 |
230 |
" ""IP emergency limit amount system manager"" exceeded" |
IPFCSM522 |
231 |
Instructed participant not reachable (offline) |
IPFCSM523 |
232 |
Requested settlement date does not correspond to the current clearing day |
IPFCSM524 |
234 |
The identification of the participant (SIC IID) does not match the settlement account. |
IPFCSM525 |
235 |
SIC RTGS service not available (offline) |
IPFCSM526 |
236 |
Customer payments not allowed |
IPFCSM527 |
240 |
Amount must be >0 |
IPFCSM528 |
241 |
IP customer payment cannot be clearly identified |
IPFCSM529 |
500 |
Internal SIC error |
IPFCSM999 |
Unmapped Error |
The following SIC codes are mapped directly to equivalent ISO codes.
SIC code |
"ISO 20022 Equivalent" |
Description |
118 |
FF01 |
Message unreadable |
119 |
FF01 |
Invalid message type |
132 |
AM05 |
Payment already exists |
133 |
PM01 |
Payment does not exist |
110 |
RM01 |
Mandatory field is missing |
123 |
RM01 |
Mandatory field is empty |
115 |
AUR01 |
No authorization |
128 |
ACC01 |
Settlement account does not exist |
135 |
RJM01 |
Invalid character(s) in the field text |
159 |
AM23 |
Amount too large |
160 |
AC01 |
Account stopped |
204 |
RJC01 |
Field not permitted in this payment type |
205 |
RM01 |
Field must be present in this payment type |
221 |
FF01 |
XML schema violation |
237 |
R70 |
Addressing the instructed participant is not allowed |
238 |
R13 |
Overall Execution Time not kept |