Outbound gCCT 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’ (Funds
Transfer/Basic Funds Transfer) (or) ‘1600’(Settlement Transfer/Basic Funds
Transfer), 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:
- Based on the Charging Method value and based on the transaction level 'gpi Enabled' flag, the Outbound message tags like Payment Notification, Charges are populated.
Note:
For ‘gpi Enabled’ Outbound Fedwire transactions, Network cutoff time validation logic remains same as existing.Parent topic: Outbound Fedwire Payments - gpi Processing