1. High Value (RTGS) Payments User Guide
  2. RTGS Processing
  3. RTGS Outbound Transaction
  4. Outbound High Value Payments Transaction Input
  5. Outbound RTGS Payment Transaction Processes

Outbound RTGS Payment Transaction Processes

Saving of Outbound RTGS Payment Transaction
  • System performs mandatory field checks & transaction validations as mentioned below while saving a transaction:
  • Charge bearer is always ‘SHA’ for RTGS payment
  • All the SWIFT related fields in Transaction have characters supported by SWIFT only
  • If Intermediary institution BIC is null then Account with institution BIC must not be null and must be a RTGS BIC
  • If Intermediary institution BIC is not null and a RTGS BIC then Account with institution BIC is not mandatory for input
  • If Intermediary institution BIC is not null and a RTGS BIC then Account with institution BIC must not be a RTGS BIC
  • For Customer Transfer, either Ultimate Beneficiary name or BIC must be present
  • For Bank Transfer,
    • If Account with Institution BIC and intermediary BIC is not present then Beneficiary institution BIC must be specified.
    • Beneficiary Institution BIC or Beneficiary Institution Name and address 1/2/3/4 is mandatory for specified
    • If Intermediary institution BIC is not null and a RTGS BIC then Beneficiary Institution BIC must not be a RTGS BIC.
  • If any of the transaction validation fails, transaction is rejected with proper error code.
  • For transaction created through upload of file or message, the transaction is moved to repair queue.
Authorization of Outbound RTGS Payment Transaction
  • On authorization, the system starts to process various payment transactions. Only the transaction whose activation date as today is picked for processing.
  • The RTGS Outbound payment would be processed through the following steps:
    • Transaction Validations
    • Account Validation (Open and Authorized record)
    • Bank Redirection
    • Account Redirection
    • RTGS Receiver Identification
    • Payment Dates Resolution
    • Processing Cut-off time check
    • Small FX Limit Check & Currency Conversion
    • Computation of Charge & Tax
    • Authorization Limit 1 Check
    • Authorization Limit 2 Check
    • Duplicate Check
    • Network Cutoff Time Check
    • Sanction Check
    • ECA Check
    • Debit /Credit Accounting Handoff
    • Message Generation
Outbound RTGS Payment - SOAP and REST web services
  • Outbound RTGS payment request received from SOAP/ REST web services is also processed as RTGS Payment.
  • If Transaction Branch is not received as part of the request, the same is populated as debit account branch. Based on transaction branch Host code is populated.
  • Host date is considered as booking date for the transaction.
  • Debit account name, debit currency, customer are derived based on the debit account number received.
  • Transactions created from requests received from SOAP/REST web services are always auto authorized.

Branch Holiday Parameter

In addition to Currency and Network Holidays, Branch holidays is considered in determining the Value date and Activation date.

Processing Branch holidays is considered in the Dates resolution only if a particular parameter in Network Preferences for the ‘Outbound’ or ‘Inbound’ transaction type is checked.

This new parameter is called ‘Branch Holiday Check.

This parameter is added to this maintenance under a new sub-section called “Value Dating Preferences”.

Parent topic: Outbound High Value Payments Transaction Input