Outbound gCCT Confirmations - MT 199 Generation
Note:
The system does not perform RMA validation on the generated gpi/universal confirmation.- Below are the additional changes to MT 199 gCCT confirmation messages generation after processing of inbound or pass through gCCT payments by the gpi bank
- Below changes are supported when the processing branch is gpi agent as per existing functionality
Note:
System do not generate MT 199gCCT confirmations if 'Generate gpi confirmations' value is unchecked (set to 'N').
Inbound transactions initiated either manually through UI or through SOAP/Rest service, 'Generate gpi confirmations' will always be set to 'N' (if not indicated).
Inbound transactions uploaded through SWIFT, 'Generate gpi Confirmations' field value will always be set to 'Y' (Checked).
Note:
The Auto job 'PQDPRQUE' - 'Job Code for Process Exception MT 199 transaction' generates the Interim gpi confirmations at EOD. Configure this job to run at a pre-defined time daily.
Transaction Type | Processing status | Message generated | Status Code/ Reason Code | Date & Time details | Payment Processing Status [PXDGPIST | In Progress Codes – gCCT [PXDGPIST] |
---|---|---|---|---|---|---|
Incoming | Processed & credited to beneficiary’s account | On accounting completion | ACCC | On accounting completion | PROCEESSED | NA |
Moved to cover match queue | By EOD, transaction is pending in cover match queue | ACSP/ G004 | Message generation Date & time | INPROG RESS | PENDINGCOVER | |
If the transaction is on hold for further documents (HOLD option in field 23 E) | By EOD, transaction is pending in Business Override queue | ACSP/ G003 | ACSP/ G003 | INPROG RESS | PENDI NGDOCS | |
Pending by EOD in process exceptions queues( including Warehouse queue) | By EOD, transaction is pending in any exception queue | ACSP/ G002 | Message generation Date & time | INPROG RESS | PENDINGCREDI T | |
Cancelled from any exception queue | On successful cancellation action | RJCT | Message generation Date & time | REJECT ED | NA | |
Transaction is Sanctions Seized | After Seizure entry posting | RJCT | Message generation Date & time | REJECT ED | NA | |
Transaction is Suppressed | On successful suppression processing | RJCT | Message generation Date & time | REJECT ED | NA | |
Pass through as SWIFT | Outbound payment Processed & forwarded as a gpi message. Message generation Suppressed | FIN message / FIN Copy service gpi message is sent out (FIN Compatible MI) | ACSP/ G000 | Message generation Date & time | NA | NA |
Outbound payment Processed & forwarded to a non-gpi agent. Message generation Suppressed | On completion of passthrough payment(on FIN/ FIN Compatible MI) | ACSP/ G001 | Message generation Date & time | NA | NA | |
Moved to cover match queue (new STP queue for Inbound Messages) | By EOD, transaction is pending in cover match queue | ACSP/ G004 | Message generation Date & time | INPROG RESS | PENDINGCOVE R | |
If the transaction is on hold for further documents (HOLD option in field 23E) | By EOD, transaction is pending in Business Override queue | ACSP/ G003 | Message generation Date & time | INPROG RESS | PENDINGCOVE R | |
Pending by EOD in process exceptions queues (including Warehouse queue) | By EOD, transaction is pending in any exception queue | ACSP/ G002 | Message generation Date & time | INPROG RESS | PENDINGCREDI T | |
Cancelled from any exception queue | On successful cancellation action | RJCT | Message generation Date & time | REJECT ED | NA | |
Transaction is Sanctions Seized | After Seizure entry posting | RJCT | Message generation Date & time | REJECT ED | NA |
- Tracker BIC address is referred from the gpi Host preferences maintenance (PXDGPIPF).
- System picks up the confirmation Status code based on the maintenance done in the screen (PXDGPIST) for the message type gCCT/gCOV.
- System picks up the confirmation Reason code based on the maintenance done in the screen (PXDGPIST) for the message type gCCT when the payment processing status is ‘INPROGRESS’.
Note:
SWIFT gpi Tracker generates gCCT confirmations to gpi agents automatically in case of ACSP/G000 and ACSP/G001, based on content of transferred MT 103 or MT 202/5 COV on FIN network. So, OBPM doesn't generate confirmation messages.