Product Description

Description

FAQ

GENISYS Money Transfer Service

Genisys is working with ICICI Bank to enhance its base of Money Transfer Agents. The retailers who sign up for this service become ICICI Bank Business Correspondent Agents after ICICI’s approval. These retailers would be permitted to make Electronic Fund Transfer/Money Transfers on behalf of customers enabling them to do remittance to any bank using IFS code and Bank account number.

About ICICI Money Transfer Service

Genisys brings to you ICICI Money Transfer, an exciting Money Transfer Service in partnership with ICICI Bank.

Now you can enroll as an ICICI Business CorrespondentAgent and change the way you do business!

Benefits for Retailers

You can provide the following to your customers using ICICI Money Transfer Service:

Domestic Money transfers powered by IMPS (Immediate Payment Service).

Online money transfer to any Bank account anywhere in India.

Service available on all days including on National and Bank Holidays.

Once the forms are received at Genisys Head Office, it will take 07 working days from the date of receipt of the forms for the Retailer verification by ICICI and subscription of the product by Genisys.

Please note that the product will be subscribed only after authorization from ICICI bank.

In case the BCA application is rejected by ICICI bank, same will be communicated to the retailer after 7 working days of the feedback from the bank.

Process:Registration and activation:

ICICI Business correspondent Agent will register a walk-in customer in the system. Customer has to provide his/her full name, complete address, active mobile number and few other details to complete the registration. Once registered, a customer can transfer money amounting to a maximum of Rs. 5,000 per transaction and Rs. 25,000 per month.
Add Beneficiary (Beneficiary is the person who you wish to send money to):

To add a beneficiary for a registered ICICI Money Transfer customer, retailer needs to enter the details of the beneficiary including name, bank account number, bank IFS code. The customer will immediately receive an OTP (one time Password) on the registered mobile number which will have to be intimated to the agent for adding the beneficiary to the customer’s account. In a year, a customer can add a maximum of 08 beneficiaries to his account. Further additions and updations are not allowed.

Deposit cash

To transfer funds to the beneficiary’s account number, customer will have to deposit cash with the authorized ICICI Business correspondent Agent. The ICICI Business correspondent Agent would initiate and complete the money transfer from his end. The customer would then receive a text message on his registered mobile number confirming the transaction details along with its transaction ID, amount transferred etc.

How is fund transferred through this process?

As soon as the agent initiates the transaction process, the system checks if the beneficiary’s bank is enlisted in the list of IMPS enabled banks. The Customer will receive an instant confirmation of the transaction on his registered mobile number. In case IMPS transfer is not possible, the system will send a request for NEFT transfer and the customer will receive a confirmation message depending on the NEFT cycle.

How much money can a Customer transfer?

You can provide the following services to your customers using Genisys ICICI Money Transfer:

Limit of Fund Transfer per transaction Rs. 5000

Limit of Fund Transfer per month Rs. 25000

Minimum Transaction Amount Rs. 100

What is the Refund Process in case of a failed transaction?

In rare circumstances it may so happen that the fund remitted to the beneficiary’s account does not get credited. For such circumstances, we have an effective remedial system in place to ensure that there is easy reversal of the failed transaction.

Every failed transaction is immediately notified to the customer through SMS and the transaction Id is provided for future referral.

Customer then visits the nearest ICICI Business correspondent Agent and furnishes his Mobile no.

The ICICI Business correspondent Agent will give the customer the complete details of the transaction and the reason for its failure.

In case of technical failure, the customer can choose to resend the amount or ask for cash refund.

Based on the customer’s reply, the agent has to initiate appropriate actions and customer will receive an OTP on his mobile.

The agent will use this OTP to process the customer’s request to either complete the transaction or refund the amount in cash.

2. Register mobile number with the bank account and get MMID from respective Bank

3. Integrate with the Acquiring Bank.

3. How does it work?

There are two ways in which IMPS merchant payments (P2M – Person-to-Merchant) transaction can be performed:

1. Customer Initiated Transaction (P2M PUSH)

2. Merchant Initiated Transaction (P2M PULL)

3.1 Customer initiated transaction (P2M PUSH)

In the customer initiated transaction (P2M PUSH), customer initiates transaction through the Bank’s mobile banking application or SMS facility provided by the Bank. The Bank offers ‘IMPS merchant payments’ form in the mobile banking application (this form is available in ‘IMPS’ menu on the main menu of mobile application) or

Payment Reference is an optional 50 characters field provided. This field will be used to enter the unique reference for the payment, and identifies the transaction to the merchant. The merchant decides what customer will enter in this field. For e.g. for insurance premium payment, customer may need to enter policy number in the payment reference field; for electricity bill payment, it may be consumer number. The syntax and information to be input in the payment reference field will be decided by merchant, and communication of the same will be merchant ownership.

The SMS syntax for making P2M PUSH transaction through SMS is as follows:

On initiating transaction as above, customer receives the confirmation SMS with status of transaction shortly.

For IMPS P2M PUSH transaction initiated through SMS, transaction limit is Rs 5,000/- per day (for most banks), and for transactions initiated through mobile banking application, transaction limit is as decided by the Bank (Rs 50,000/- for most banks)

3.2 Merchant initiated transaction (P2M PULL)

In Merchant Initiated transaction (P2M PULL), the transaction is initiated through Merchant application (such as Merchant website, WAP site, IVR, mobile application). The typical steps to follow for making transaction through P2M PULL are as follows:

a. Visit merchant application such as web site, mobile application, or WAP site

b. Select product / service for which payment is to be made

c. In the payment options available, choose IMPS

d. Enter credentials as follows:

i. Customer mobile number

ii. Customer MMID

iii. OTP (One-Time Password)

e. The transaction status is displayed on the screen

The customer needs to enter the credentials – Customer mobile number (as registered with the Bank), customer MMID (as generated by Bank) and OTP (One-Time Password, as generated by customer). OTP needs to be generated by customer for each transaction. OTP can be generated by customer by using mobile banking application or SMS facility as provided by the Bank. The Bank offers ‘Generate OTP’ form in the mobile banking application (this form is available in ‘IMPS’ menu within main menu of mobile banking application) or SMS syntax for ‘Generate OTP’ transaction. Customer needs to enter the following parameters:

1. M-PIN

The SMS syntax for ‘Generate OTP’ through SMS is as follows:

OTP <M-PIN> to Bank’s long code or short code number.

On initiating transaction as above, customer receives the confirmation SMS with status of transaction shortly.

a. The OTP generated as above has following characteristics:

1. OTP is valid for 1 hour from time of generation

2. If OTP is generated through SMS, the transaction limit is Rs 5,000/- and if OTP is generated through mobile banking application, the transaction limit is as decided by the Bank (Rs 50,000/- for most banks)

3. OTP is valid only for one transaction – Successful or Failure

a. 4. Only one OTP (latest generated OTP) is valid at a time

4. What are the use cases for P2M PUSH transactions?

Following are the use cases for P2M PUSH transactions:

1. Insurance premium payment

2. Mobile / DTH Recharge

3. Fee payments

4. Credit card payments

5. Utility Bill payments

6. Over-the-counter payments

7. Face-to-face payments – Pizza delivery, Courier, Cabs, Retail

5. How does customer make face-to-face payment using IMPS P2M PUSH?

Customer can make P2M PUSH payment to the enterprise using enterprise mobile number, MMID, and enter amount, payment reference, and M-PIN, in the mobile banking application or SMS / USSD facility provided by the Bank. The customer as well as enterprise shall receive confirmation SMS.

In case of face-to-face payments, the customer may be paying to the agent of enterprise (such as pizza delivery person, or courier agent), and it is important for the receiving agent to get an SMS confirming the transaction. So even if enterprise receives an SMS, the agent in front of customer doesn’t know about the transaction status. To take care of this issue, enterprise can register multiple mobile numbers (mobile numbers belonging to enterprise agents) with their respective Bank. Customer initiates payment using agents mobile number and MMID, and the payment is received into the enterprise account (since agent mobile number / MMID is linked with enterprise account). The customer as well as agent shall receive confirmation SMS.

6. What are the use cases for P2M PULL transactions?

The use cases for P2M PULL transactions are as follows:

1. Mobile POS

2. Merchant aggregators

3. Retailers, FMCG, Food chains

4. E-commerce, movies, classified, courier

5. Travel & Ticketing, Radio Taxi

6. Mutual Funds

7. Insurance

8. Utility Bill Payments

9. Mobile / DTH recharge

10. Trading / NBFC

11. Credit Cards

12. Fees payments

13. Donation

7. What is Mobile POS application?

Mobile POS is the mobile application that can be downloaded by merchant on their phone. Merchant can receive payment from customer via IMPS using the mobile POS application. Enterprise may comprise of multiple agents that receive payments on behalf of enterprise (such as agents at cash counters, pizza delivery agents, courier agents, taxi drivers, etc). The agents mobile number can be linked to the enterprise bank account at the Bank end, and the agent can receive payment from customer on behalf of enterprise, by using application on their mobile phone.

The process is as follows:

1. Enterprise agent has mobile POS application on the phone

2. Opens up form ‘Receive payment from customer’

3. Enters payment reference, amount

4. Asks customer to enter mobile number, MMID and OTP

5. Agents mobile number (through which payment is initiated) is linked with merchant account

6. Merchant account is credited and customer account is debited

7. Customer and agent get confirmation SMS

8. Facility to link multiple mobile numbers and MMID with one account, so payments can be received in single account of merchant / aggregator

Mobile POS application can be given by retail organizations at their cash counters. Virtual POS can be deployed at the cash counters as well, in which customer can make payment by providing their mobile number, MMID and OTP, and the cash counter person shall enter this information in the virtual POS application on their PC. This can be integrated with billing system of the retailer as well.

The mobile POS can be used by courier agents and receive payments via IMPS. Cash on delivery can be replaced with payment via IMPS. This can help reduce cost and settlement cycle can be reduced. Insurance agents can carry mobile POS application as well and collect payment from customers using mobile POS instead of cash and cheque. There is no investment required for the POS machines and no need for agents to visit insurance company branch office to submit cash and cheque. In Mutual Funds, customers can pay to distributors via Mobile POS.

8. What are the advantages for payment via IMPS?

The advantages of payment via IMPS are as follows:

1. Number of mobile users is lot more. Mobile number can be linked to bank account for everyone

2. Replacement of cash

3. Remote payments – via website, IVR, mobile application

4. Mobile POS

5. No investment on POS machine for receiving payment via IMPS

6. Convenience, anytime, anywhere payments

9. What are the amount limits for transactions through IMPS merchant payments?

The amount limits for transactions with end-to-end encryption is as follows:

Regarding OTP transaction limits, If OTP is generated through unencrypted channels, the transaction limit is Rs 5,000/- and if OTP is generated through encrypted channels, the transaction limit is as decided by the Bank (Rs 50,000/- for most banks, as of now)

10. How can the merchant get on-boarded on IMPS merchant payments?

The merchant can get on-boarded on IMPS merchant payments through any of the following:

For list of services available on IMPS merchant payments, please visit http://www.npci.org.in/impsmerpay7.aspx.

This includes services available through merchant aggregators.

10.1Timeout scenarios

During Debit – Between Issuing Bank and its CBS. Reversal will be generated by Issuing Bank system to CBS and the transaction is not processed further. Customer is appropriately informed

After Debit Between Issuing Bank and NPCI – Issuing Bank will treat this as time-out transaction.

Issuing Bank will send out Verification Request giving the reference number of the original transaction

to NPCI. Verification request is sent post time-out period of original transaction (30 seconds). Issuing Bank may send max up to 3 verification requests for one transaction, if it does not receive a response. Acquiring Bank will respond to this request as per status of original transaction (“00” for successful verification and credit transaction and “M0” for credit not successful but verification is successful). Based on response to this request, Issuing Bank shall reverse the earlier debit (if response code is “M0”). After Debit between NPCI and Acquiring Bank – This transaction is responded by time-out response Code by NPCI and send to Issuing Bank. Upon receiving a time-out response, Issuing Bank will send out a verification request giving the reference number of the original transaction to NPCI. Verification request is sent post time-out period of original transaction (30 seconds). Issuing Bank may send max up to 3 verification requests for one transaction, if it does not receive a response. Acquiring Bank will respond to this request as per status of original transaction (“00” for successful verification and credit transaction and “M0” for credit not successful but verification is successful). Based on response to this request, Issuing Bank shall reverse the earlier debit (if response code is “M0”). After Debit between Acquiring Bank switch and CBS – This transaction is responded by time-out Response code by Acquiring bank to NPCI and NPCI passes it to Issuing Bank. Issuing Bank will send out a verification request giving the reference number of the original transaction to NPCI. Verification request is sent post time-out period of original transaction (30 seconds). Issuing Bank may send max up to 3 verification requests for one transaction, if it does not receive a response. Acquiring Bank will respond to this request as per status of original transaction (“00” for successful verification and credit transaction and “M0” for credit not successful but verification is successful). Based on response to this request, Issuing Bank shall reverse the earlier debit (if response code is “M0”).

· Documentation to prove there was no credit adjustment raised by the acquiring bank

IMPS Merchant Payments – For Banks and Merchants

107 Duplicate processing RRN number of first transaction must be provided. The merchant name and location, transaction amount, payment reference (if provided), and the transaction date must be the same. Issuers must review transactions presented with ticket numbers closely. If the ticket numbers are different, the transactions are not considered duplicates, although the merchant locations, transaction amounts, and transaction dates may be the same

12. How does merchant get integrated with Acquiring Bank?

Integration kit is shared between Merchant and Acquiring Bank, and integration carried out accordingly.

12.1 For push transactions

Acquiring bank should be able to integrate with merchant back-end system for payment reference verification and update of merchant back-end system after transaction is complete

12.2 For pull transactions

API to be provided by acquiring bank to merchant for integration with merchant website / WAP application For SMS / IVR / mobile handset application, the following integration could be required with merchant application:

1. Pre-payment integration – before the payment, the merchant payment reference data may need to be verified. This can be done through the pre-payment merchant URL, where merchant URL is called and payment reference field is passed. If successful response is received, further processing is done for payment transaction, otherwise error message is sent

2. Post-payment integration – after the payment, the merchant back-end system may be called to update the transaction status at the back-end

The above two can be configured in the merchant technical configuration of the merchant account

Verification integration – If response is not received by merchant for transaction request, merchant should be able to call verification URL for verifying transaction status at acquiring bank.

IMPS Merchant Payments – For Banks and Merchants

13. What are the various interfaces through which merchant can receive payment via IMPS merchant payments PULL transaction?

Acquiring bank needs to provide an application to merchant to receive payment.

Acquiring bank will provide a payment web page. This will be integrated with merchant website. Customer will be redirected to this webpage during the payment step of the transaction. The following parameters will be passed from merchant website to the payment web page:

1. Merchant user name

2. Merchant password

3. Merchant IP address

4. Amount (if pre-populated)

5. Customer mobile number (if pre-populated)

6. Payment reference (if pre-populated)

The payment web page will validate the merchant details, such as user name, password, IP address, and allow payment only if validation is successful

The above page will contain following input fields from customer:

1. Customer mobile number

2. Customer MMID

3. OTP

4. Amount (pre-populated, if available)

5. Payment reference (pre-populated, if available)

This will be a secure page. Information from the secure page will be sent to the acquiring bank switch. Following parameters will be sent to acquiring bank switch:

1. Merchant mobile number

2. Merchant MMID

3. Customer mobile number

4. Customer MMID

5. OTP

6. Amount

7. Payment reference

13.2 WAP application for integration with merchant WAP site

IMPS Merchant Payments – For Banks and Merchants

Similar to above web application

13.3 IVR application

Acquiring bank will provide an IVR number to merchant for receiving payments. Merchant can call the IVR number, and will be prompted to enter merchant ID. If merchant calls from his registered mobile number or phone number, the step to capture merchant ID can be skipped. Upon identifying the merchant, IVR will prompt to enter amount. Merchant will then be asked to conference the customer with the IVR call. Customer will get the confirmation of merchant name, and amount to be paid, will be prompted to asked to enter mobile number, MMID, and OTP. The information will be sent to acquiring bank switch, and IVR will wait for transaction status to be received. Once the transaction status is received, customer will be informed about the same on the IVR call.

13.4 Merchant mobile handset application

Acquiring bank can provide a mobile handset application to the merchant. Merchant downloads the application on his handset and registers his mobile number with the acquiring bank. The application has a ‘Receive payment’ form on the handset application.

For receiving payment from customer, the merchant enters customer mobile number, MMID, OTP, amount, and payment reference. Merchant is identified from the mobile number from where the request is initiated. The transaction status is received on the mobile handset application of merchant.

Merchant can initiate payment via SMS for receiving payment from customer. Merchant registers his mobile number with his merchant account with the acquiring bank. From his registered mobile number, merchant sends SMS with following parameters:

1. Customer mobile number

2. Amount

3. Payment reference

An IVR call or USSD message is made to the customer mobile number, and is prompted for merchant name, amount and is asked to confirm or reject the transaction. Alternatively, merchant sends SMS with customer mobile number, MMID and OTP.

Upon confirmation, customer will be asked to enter MMID, and OTP.

IMPS Merchant Payments – For Banks and Merchants

Upon successful transaction confirmation, an SMS will go to customer as well as merchant.

13.7 Reminder SMS based application

Merchant can send a reminder SMS to customer for payment. The SMS will contain details about the payment. Customer will respond to the SMS with a reply SMS, and will send following parameters in the SMS:

1. Merchant ID

2. Amount

3. Payment reference

4. Customer MMID

5. OTP

The acquiring bank will receive the SMS, will validate the various information, along with payment reference, and does transaction processing through NPCI Upon successful transaction confirmation, an SMS will go to customer as well as merchant.

13.8 Merchant server application

Customer can call merchant call center for ordering product /service and making payment. The agent will help customer with the order, and enter following information in his merchant server application:

1. Customer mobile number

2. Amount

3. Payment reference

Merchant will initiate the payment transaction upon entering the above information. Customer will receive an IVR call or USSD message on his mobile and will prompted for merchant name, amount and is asked to confirm or reject the transaction.

Upon confirmation, customer will be asked to enter MMID, and OTP.

Upon successful transaction confirmation, an SMS will go to customer as well as merchant.

13.9 USSD based application

Merchant can initiate payment transaction via USSD. Acquiring bank to provide USSD number to the merchant. Merchant initiates transaction through the USSD number. A form is sent by the USSD server to the merchant, and merchant is prompted to enter customer mobile number, amount, and payment reference. Upon entry of these details, a USSD message or IVR call will be sent to customer and will be prompted for merchant name and amount and will be asked to confirm or reject the transaction. Upon confirmation, customer IMPS Merchant Payments – For Banks and Merchants will be asked to enter customer MMID, and OTP. Alternatively, merchant enters customer mobile number, MMID and OTP on the USSD form. Upon successful transaction confirmation, an SMS will go to customer as well as merchant.

13.10 STK based application

The merchant transaction initiation form will be available on the merchant SIM card. Merchant accesses the form on the SIM card for initiating payment from customer, and enters following parameters

1. Customer mobile number

2. Amount

3. Payment reference

An IVR call or USSD message is sent to the customer mobile number, and is prompted for merchant name, amount and is asked to confirm or reject the transaction. Upon confirmation, customer will be asked to enter MMID, and OTP. Alternatively, merchant enters customer mobile number, MMID and OTP on the USSD form. Upon successful transaction confirmation, an SMS will go to customer as well as merchant.

13.11 WAP based application

Merchant can access the WAP site provided by acquiring bank for initiate payment transaction from customer. Merchant can log on to the WAP site, and can access payment initiation page. Merchant will enter customer mobile number, amount, payment reference.

An IVR call or USSD message is sent to the customer mobile number, and is prompted for merchant name, amount and is asked to confirm or reject the transaction. Upon confirmation, customer will be asked to enter MMID, and OTP. Alternatively, merchant enters customer mobile number, MMID and OTP on the USSD form. Upon successful transaction confirmation, an SMS will go to customer as well as merchant.

13.12 Internet based application

Merchant can access the Internet site provided by acquiring bank for initiate payment transaction from customer. Merchant can log on to the web site, and can access payment initiation page. Merchant will enter customer mobile number, amount, payment reference.

An IVR call or USSD message is sent to the customer mobile number, and is prompted for merchant name, amount and is asked to confirm or reject the transaction. Upon confirmation, customer will be asked to enter MMID, and OTP. Alternatively, merchant enters customer mobile number, MMID and OTP on the USSD form. Upon successful transaction confirmation, an SMS will go to customer as well as merchant. IMPS Merchant Payments – For Banks and Merchants

14. What is the merchant configuration required at the acquiring bank platform?

The following configuration needs to be there in the acquiring side platform:

14.1 Merchant set-up

Acquiring bank could set up the merchant account through web interface. Access should be provided on need basis to required personnel. Bank should be able to enter following information related to the merchant:

If real-time validation is required, the pre-payment URL is required to be configured

If real-time status update is required, the post-payment URL is required to be configured

If confirmation SMS is required, merchant mobile number is required to be configured where SMS is to be sent If confirmation email is required, merchant email is required to be configured where email is to be sent

14.3 Financial configuration

The following financial configuration is required to be configured:

1. Transaction fee from merchant

15. What facility is required for transaction status verification for merchant?

An interface should be provided to merchant to verify the transaction status. This is useful in case the transaction is complete, but merchant doesn’t get to see the transaction status.

IMPS Merchant Payments – For Banks and Merchants

An online API to be provided to merchant that can be used to check transaction status as exception handling process. In case merchant does not get transaction status, he can call this URL 3 times in 30 seconds interval and get transaction status.

Apart from exception handling, this interface can be used for getting ad-hoc transaction status as well.

16. What are the security guidelines for acquiring Bank and merchants?

· The Merchant needs to have necessary information security controls in place. – Merchant should be

Educated that critical data processed in IMPS transactions are important and equivalent to card holder data in debit or credit card transactions or any other bank transactions. They need to follow industry best practices when it comes to protect business critical data

· OTP should not be displayed on the merchant application end user screen in clear text

· HTTPS is mandatory between Merchant and Acquirer

· Acquirer needs to have strong authentication process for the merchant which includes IP address,

username and password over encrypted channel

· Issuer need to adhere strictly on time validation since OTP generation (1 hour for all banks)

· The OTP will be used only for one transaction (either successful or failure)

· OTP length should be minimum of 6 digits and should be adhered by Issuer as well as Acquirer

· Triple DES encryption needs to be in place

· OTP and other transaction details from merchant end will traverse on secure channel (HTTPS)

· OTP will be encrypted at all times using TDES during the transaction process

· OTP transmission from acquirer bank to NPCI to issuing bank can be encrypted/decrypted using HSM encryption or software encryption.

· Mobile number and MMID of customer, if shared with merchant, should be masked by default, by

Acquiring bank. In case of MMID, the last 3 digits can be masked. First 4 digits comprising of NBIN can be left unmasked for easy recognition of issuer bank. However, sharing of customer mobile number and MMID with select merchants is allowed as per the discretion of the acquirer bank. The liability of misuse of customer mobile number and MMID lies with the Acquiring Bank. Acquiring Bank should take necessary precautions for the security and confidentiality of the data and if required as per the discretion of the Acquiring Bank this can be shared only with select personnel of the merchant

OTP should not be stored on merchant application (Just like PCI DSS does not allow storage of

Authentication data like CVV, PIN, PIN Block, Mag Stripe data)

· Merchant or aggregator application must follow secure application development and deployment

practices.

· Merchant or aggregator application must have undergone application security testing comprising of