Return message upload
ReST service is provided for uploading the Return transactions received for Outbound CNAPS Credit transaction. The following fields are available in the service:
- Source Reference
- Return Message ID
- Original Transaction Reference
- Host Code
- Network Code
- Payment Method (H -HVPS, B -BEPS, O- BEPS Real-time)
- Return Currency
- Return Amount
- Customer Account
- Customer Name
- Reason Code
- Return Reason
- Return Remarks
Debit accounting is posted upfront as below:
| Event | Dr/ Cr | Account | Account Type | Amount Tag |
|---|---|---|---|---|
| HSDR | Dr | Nostro/Network Clearing GL | GL | Transfer Amount |
| HSDR | Cr | Intermediary GL | GL | Transfer Amount |
The system tries to match the Original transaction reference with the outbound transaction present in the system and marks the Transaction status of the original transaction as 'Return Received'. If the original transaction is not found in the system with 'Processed' status, appropriate error is logged for the return transaction.
Original transaction is not available in the system or the transaction status is not valid.
If the original transaction is matched and the Customer account is not matching with the original account, the following error is logged:
“Customer Account" received is not matching with the original account
Return transactions are moved to Outbound CNAPS Reject Queue (Function ID: PQDCNRJQ). The Reject Type is 'Return' and Reject Status is 'Unprocessed'
Figure 3-18 Outbound CNAPS Reject Queue
The following actions are available in CNAPS Reject Queue:
- Accept
- Re-initiate
- Authorize
- Delete
- Reject
- View Queue Action
- View Original Transaction
Every action except the View actions require user Role/Queue access rights enabled. Accept/ Re-initiate actions require authorization.
Note:
This Queue is common for Outbound CNAPS Credit/Debit. The reject types supported are Return and Network Reject.Parent topic: Return of Outbound CNAPS Credit Transactions