2.3.1 CNAPS Inbound Payments Transaction Input

The CNAPS Inbound Payments Transaction Input screen allows users to manually create a CNAPS Inbound Payment by providing the details.
  1. On Homepage, specify PHDITONL in the text box, and click next arrow.
    CNAPS Inbound Transaction Input screen is displayed.

    Figure 2-20 CNAPS Inbound Transaction Input

    Description of Figure 2-20 follows
    Description of "Figure 2-20 CNAPS Inbound Transaction Input"
  2. Click New button on the Application toolbar.
  3. On CNAPS Inbound Transaction Input screen, specify the fields.
    For more information on fields, refer to the field description below:

    Table 2-12 CNAPS Inbound Transaction Input - Field Description

    Field Description
    Transaction Branch System defaults the transaction branch code with the user’s logged in branch code.
    Host Code System displays the Host Code of selected branch of the logged in user on clicking ‘New’ button.
    Network Code Select the Network Code from the list of values. All networks of payment type CNAPS are listed based on Network Code maintenance.

    Based on the Network selected, payment type gets populated. If only one Network is defined, that Network is defaulted on ‘New’ operation itself.
    Payment Method Select the payment type from the following:
    • HVPS - High Value Payments System
    • BEPS - Bulk Electronic Payment System
    • BEPS - Real Time
    Transfer Type Select the transfer type from the drop-down list. System defaults the transfer type as ‘Customer Transfer. The list displays the following values:
    • Customer Transfer
    • Bank Transfer
    Source Code Select the Source Code from the list if values. All valid source codes maintained in the Source Maintenance, are listed here.
    Transaction Reference Number System generates the transaction reference number. For more details on the format, refer the Payments Core User Guide.

    This is a unique identifier of the CNAPS payment transaction and auto-generated by the system based on the common transaction reference generation logic. The same reference is used as Message ID.
    Sender’s Reference Specify the Sender’s Reference.
    End to End Identification Specify the End to end ID provided by the originating customer (debit account owner). This is a mandatory field.

    If not provided by the customer, system populates the transaction reference number automatically on saving the transaction.
    Source Reference Number Specify the Source Reference number. The external system reference can be input in this field. This is optional for manually input transaction and is mandatory for channel input transactions.

Parent topic: CNAPS Credit Inbound Payments