Outbound gCOV Processing
gpi enabled Transaction:
When you select the Business Function Code as ‘CTP’, Local Instrument value
[{3610}] as ‘COVS’, and Type & Subtype(combined) value as ‘1000’ (or)
‘1600’, system performs below validation:
- Checks whether ‘gpi Processing Enabled’ is set to ‘Y’ at host level (PXDGPIPF).
- When the ‘gpi Processing Enabled’ flag is set to ‘Y’, then system checks 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 (PMDGPIDR).
- When ‘Yes’, then the transaction is set as ‘gpi enabled’ and is processed as a SWIFT gpi transaction.
- When ‘No’, then the ‘gpi enabled’ flag is set as ‘No’ and the transaction is processed as normal SWIFT transaction.
Fedwire message generation:
At the transaction level, if the ‘gpi Enabled’ flag is ‘Yes’, then the tag {3620}
populates as below:
- §Tag {3620} Element 01 Payment Notification Indicator populates with a value ‘3’
- §Tag{3620} Element 03 Contact Name populates with UETR value
| Tag | Tag Name | Element Name | Format | Population Logic |
|---|---|---|---|---|
| 3620 | Payment Notification | Element 01 – Notification Indicator | 1 Character | Value ‘4’ hardcoded gets populated |
| 3620 | Payment Notification | Element 03 – Contact Name | 140 Character | UETR value gets populated |
Note:
For ‘gpi Enabled’ Outbound Fedwire transactions, Network cutoff time validation logic remains same as existing.Parent topic: Outbound Fedwire Payments - gpi Processing