1. Cross Border User Guide
  2. SWIFT gpi
  3. gCOV Transaction Processing
  4. Outbound gCOV processing (Debtor/ Instructing Agent)

Outbound gCOV processing (Debtor/ Instructing Agent)

  • gCOV Transaction:

    If the ‘gpi Enabled’ customer transfer is done through cover method, the cover message will be treated as gCOV message for ‘Cross Border’/’RTGS’ payment types.

    - Block 3 gpi tags ‘111’ will be populated with value ‘001’. System automatically picks up the service id based on the maintenance done in the screen (PXDGPIST) for the message type gCOV

  • Currency Cut-off Time Check:

    - In case of gCOV cover method (as part of gCCT processing), system considers only the gCCT leg currency cut-off time for processing Outbound payments. (i.e. System will not check the receiver cutoff time for the Receiver of Cover).

Pass Through gCOV Processing (Reimbursement Agent)

Following are the changes required to process Pass-through payments:
  • ‘Inbound gpi’ checkbox
    • ‘Inbound gpi’ check box is set to 'Y' if an Inbound payment (MT 202COV/MT 205COV) has gpi tags (111:001) and is resulting in an Outbound payment (gpi/nongpi).
    • ‘Inbound gpi’ check box is set to 'N' if an Inbound non-gpi payment resulting in an Outbound payment(gpi/non-gpi).
  • ‘gpi enabled’ Check:
    • System first checks if ‘gpi Processing Enabled’ flag is set to ‘Y’ at host level (Function ID: PXDGPIPF). If Yes, system applies gpi payments processor logic. If No, it is processed as normal SWIFT payments.
    • If ‘gpi Processing Enabled’ flag is set to ‘Y’, then system will check
    • Sender BIC (Processing branch BIC – Default BIC (11-character) linked in Branch Core Parameters screen (STDCRBRN)) and Transfer Currency combination is present in SWIFT gpi Directory (Function ID: PMDGPIDR).
    • If ‘Yes’, then the transaction is stamped as ‘gpi enabled’ and is processed as a SWIFT gpi transaction.
    • System populates gpi tags ‘111’ with value ‘001’ and ‘121’ with same UETR as the underlying Inbound gCOV in FIN block 3 of MT 202COV/205COV.
    • If ‘No’, then the ‘gpi enabled’ flag is set as ‘No’ and the transaction is processed as normal SWIFT transaction.
    • System performs validations and processing as applicable for Outbound ‘gpi enabled’ transactions as detailed in previous section.
  • Currency Cut-off Time Check:
  • Below validations are done when Inbound cover message resulting in an Outbound gCOV:
    • If Receiver of MT 202COV/205COV BIC, CCY is identified as gpi agent as per gpi directory then system will check if Outbound gpi payment receiver agreement is present in the new screen (PXDSROAG).
    • If present, Outbound cut-off time is considered from here.
    • If not, Outbound cut-off time is taken from the gpi directory for the Receiver BIC, Currency combination.
    • If the transaction passed this cut-off time, then the transaction moves to Network cut-off queue.
  • MT 202COV/MT 205 COV - Fields 52A, 57A Population:

    For gpi enabled ‘Cross Border’ payments, changes will be done to populate Field 57A even if AWI is same as that of Receiver of the message. Field 52A, as applicable (Ordering Institution), 58A (Beneficiary Institution) will be populated in the gCOV MT 202COV/MT 205COV message generated.

    • Field 52A: In case of pass thru, 52A is added if in the Inbound MT COV this field is absent.
    • Field 57A is populated even if AWI is same as that of Receiver of Outbound cover payment message.

Parent topic: gCOV Transaction Processing