2 External Payments Interface

This topic describes the External Payments Interface (EPI), which provides the capability of interfacing with merchant websites.

The application supports the facility to interface with third party systems. Through the support of external payment interfaces, the bank’s customers can make purchases from merchant sites by using their bank accounts. A transaction through EPI is performed as follows:

• A customer logs on to the merchant site. This could be an online shopping site, online travel booking or any other site where the customer is required to initiate a payment towards a merchant.
• The customer reaches the page on the merchant’s site wherein he is required to select a mode of payment. The customer selects the mode of payment as bank account and selects the bank.
• The customer is redirected to the bank’s internet banking URL wherein he is required to enter his login credentials.
• On successful verification of the customer’s login credentials, the screen on which the customer can verify the defaulted account number and confirm the transaction appears.
• If no account number is defaulted, the customer can select the account from which the funds are to be debited and can then proceed to confirm the transaction.
• The customer is redirected to the merchant site on which the status of the transaction is displayed.

Pre-requisites:

• Transaction access is provided to business user
• CASA accounts are maintained in the host system under a party ID mapped to the user
• Merchants are maintained within OBDX

To perform a transaction through EPI:

1. Login to the Merchant URL.
2. From the Merchant Site URL, click External Payments Interface
   The Merchant Details screen appears.

   Note:

   The following Merchant Details screen is a dummy merchant screen and the fields indicate the parameters to be received by the Bank portal from the Merchant portal.

   Figure 2-1 Merchant Details

   
   

   
   Description of "Figure 2-1 Merchant Details"

   
   

   Note:

   The fields which are marked as Required are mandatory.

   For more information on fields, refer to the field description table.

   Table 2-1 Merchant Details - Field Description

   Field Name	Description
   Merchant Code	The unique key assigned to a specific merchant by the bank.
   Success Static URL Flag	Whether the flag of URL for sending the static response for a successful transaction is checked or not.
   Failure Static URL Flag	Whether the flag of URL for sending the static response for unsuccessful transaction is checked or not.
   User Account Number	The user’s account number from which amount is to be debited.
   Merchant Reference Number	The reference number that is passed from the merchant site.
   Transaction Amount	The amount to be paid to the merchant.
   Service Charges	Displays the service charge amount to be debited, if any.
   Checksum Value	Specify the checksum value.
   Base URL	Base URL of an application to be passed on.
   Default URL	Default version of an application to be passed on.
   Additional Detail 1, 2, 3	Specify additional details if any.
   Entity	Entity to which the merchant belongs to be passed on.

3. In the Merchant Code field, enter the ID of the merchant.
4. In the User Account Number field, select the account number of the user that is to be debited (The user needs to mandatorily select the account number, only if ‘Default customer’s debit account number as request parameter’ check box is not selected by bank administrator in the ‘Merchant Maintenance’ screen).
5. Enter the other relevant merchant details.
6. Click Submit.
   The user will be redirected to the bank portal from the merchant site.

   Figure 2-2 Bank Portal

   
   

   
   Description of "Figure 2-2 Bank Portal"

   
   
7. Enter your login credentials.
8. Click Login.
   The External Payments Interface – Complete Payment screen appears.

   Figure 2-3 External Payments Interface – Complete Payment

   
   

   
   Description of "Figure 2-3 External Payments Interface – Complete Payment"

   
   

   Note:

   The fields which are marked as Required are mandatory.

   For more information on fields, refer to the field description table.

   Table 2-2 Field Description

   Field Name	Description
   Transfer From	The account from which the amount is to be transferred. Account number gets defaulted if user has only one CASA or Default customer’s debit account number as request parameter flag is set as ‘Yes’ by the selected merchant. Otherwise, user gets an option to select an account number from which the amount needs to be debited.
   Transfer To	Name of the merchant.
   Merchant Reference	Reference number of the merchant.
   Amount	The payment amount to be transferred from the account is displayed as a read only field.

9. Click Submit to pay.
10. The Review screen appears.
    Perform one of the following actions:

    • Verify the details and click Confirm.
    • Click Cancel to cancel the transaction.
11. The details submitted by the user will be updated in the host system. The success message appears along with the reference number.