GeM Pool Account (GPA) integration

[Audio] Namaskar! Welcome to Government e-Marketplace.

[Audio] In this module, we will introduce you to GPA ( GeM Pool Account), GeM pool account process flow, GPA Models and the Process of Integration of Banks in GeM pool account The topics covered in this module are: Introduction to GPA Introduction Mechanism.

[Audio] Introduction to GeM Pool Account ( GPA) GeM Pool Account (GPA), is a special purpose bank account opened, operated and controlled exclusively by each Buying agencies/ organizations of GeM. The Buying Organization/ Agency can open GeM Pool account in any of the GPA enabled bank. To enable the bank for GPA, the Bank has to integrate with GeM Portal using API integration mechanism. Currently we have 18 Banks integrated for GeM pool account The GPA integration is a standardized integration model and every bank gets on boarded on the Generic solution . The details of the Integration and API details are available in Gem Pool account Technical Design document. The GPA Integration Technical design document is available on GeM Homepage under Integration toolkit. You can download the document and start Integration process..

[Audio] Introduction to GeM Pool Account ( GPA) GeM Pool Account (GPA), is a special purpose bank account opened, operated and controlled exclusively by each Buying agencies/ organizations of GeM. The Buying Organization/ Agency can open GeM Pool account in any of the GPA enabled bank. To enable the bank for GPA, the Bank has to integrate with GeM Portal using API integration mechanism. Currently we have 18 Banks integrated for GeM pool account The GPA integration is a standardized integration model and every bank gets on boarded on the Generic solution . The details of the Integration and API details are available in Gem Pool account Technical Design document. The GPA Integration Technical design document is available on GeM Homepage under Integration toolkit. You can download the document and start Integration process..

[Audio] The GeM Pool account has 2 Models - Challan model Funds are transferred in the GeM Pool account after the demand/ intent has been finalized. A Challan is generated on GeM using which the Buyer funds the required amount in GeM Pool Account. Non Challan model A Floating amount based on Procurement forecast is maintained by Buyer in the GeM Pool Account. No challan is generated as GeM Pool Account is already funded..

[Audio] Pre Requisites for GPA Integration IP Whitelisting Whitelisting of GeM IP by the Bank. GeM Public IP will be shared to banks and Banks have to whitelist that IP Whitelisting of Bank IP by GeM . banks will share their Public IP and GeM will whitelist the IP> Kinldy note that Port by default will be 443. Signoff on Technical Design Document Banks will give a signoff of the GPA technical Design document Alignment of Bank Technical and Development Team For development of required API and integration, the Bank will have to align the respective Technical and development team ..

[Audio] The following are the API that compose the GeM pool account. The Bank shall have to develop these API and share with GeM for consumption. There are 7 API to be developed by Banks. The service structure of these API is also available in Technical design document..

[Audio] Account validation API – To onboard the GeM Pool account on geM portal, the Buying organizations would open the GeM Pool account with the Bank. Once the account is opened, they would then Onboard the GeM pool account on the GeM portal. The GeM portal would send the request to the bank via this API to validate the bank account. Once the Bank confirms the bank account is correct, the GeM portal would make the account active for the Buying organization. The following Information is shared by GeM portal with Bank Account Number, IFSC Code, Account Holder Name, Account Holder Email The following information is shared by Bank with GeM Portal in Response Account verification status, Mode of Operation, Account holder email verification, Account holder email id.

[Audio] DDO mapping API Drawing & disbursing officer is a user authorized for Payments in Buyer Organization. Also called paying accounts officer DDO Mapping generates a unique identifier for the DDO user on GeM portal for the Buying Organization. GeM sends the DDO information to the bank to Register the DDO Bank Maps the DDO user to the GeM pool account. A pool account can have multiple DDO users The following Information is shared by GeM portal with Bank Organization code, GPA account details, DDO code The following Information is shared by Bank with GeM Portal in Response Registration Status, DDO Bank registration id.

[Audio] Challan Generation API This Services Generates the Challan for Funding the GeM pool account. This service would be used only if the Buying Organization has opted for Challan model of GPA Once the Buyer finalizes the Purchase on GeM portal via any of the available procurement modes – Direct Purchase, Bid, RA, the GeM portal sends the details to the Bank The Bank generates the challan which is shown to User with option to download and print The following Information is shared by GeM portal with Bank Organization code, GPA account details, DDO code, Amount, Ref id The following Information is shared by Bank with GeM Portal in Response Challan token, Status.

[Audio] Balance Enquiry API Purpose of this interface is to enquire on the Pool account balance. In challan mode, the service would return the balance for a particular challan id generated by the buyer. In Non Challan mode, the service would return the balance in the GeM Pool account. GeM portal allows user to continue ahead with finalization of Order only when the balance is available The following Information is shared by GeM portal with Bank Unique Ref No, Challan number, GPA bank details, DDO code The following Information is shared by Bank with GeM Portal in Response Balance amount.

[Audio] Fund Blocking and Unblocking API The Purpose of this interface is to send the Blocking or Unblocking request from GeM portal to Bank. Banks on receipt of the Request would Block the funds in the pool account or Unblock the funds The following is the Process workflow for Blocking of Funds On GeM Portal, the Buyer Raises the Request to block the Funds on GeM portal GeM Portal shares the details with bank Bank marks a lein in GeM pool account and generates the unique id Buyer proceeds with Order placement post confirmation from bank. The following is the Process flow for Unblocking the funds Buyer raises the request to unblock the funds GeM sends the details to bank for confirmation Bank removes the lein in GeM pool account The Unblocking confirmation is saved and displayed to the Buyet The following Information is shared by GeM portal with Bank Order Number, Blocking amount, Challan Number The following Information is shared by Bank with GeM Portal in Response Fund Blocking confirmation status, Blocking Ref id..

[Audio] The Unblocking confirmation is saved and displayed to the Buyet The following Information is shared by GeM portal with Bank Order Number, Blocking amount, Challan Number The following Information is shared by Bank with GeM Portal in Response Fund Blocking confirmation status, Blocking Ref id..

[Audio] Payment Status API Purpose of this interface is to get the status of the Payment request to check if the Payment is credited to the beneficiary. The following is the process Flow of the API Buyer enquires on the status of the Payment on GeM portal GeM sends the details to bank for confirmation Bank checks the Payment status and sends the confirmation back GeM closes the Transaction and marks the Bill to paid. The following Information is shared by GeM portal with Bank Payment reference number The following Information is shared by Bank with GeM Portal in Response Status of Payment, Credit date, Credit status.

[Audio] Error and failure Handling Mechanism The GPA Integration has Error codes are implemented to handle specific error occurring at the bank and any Failure in Response when GeM make request to different APIs endpoint. The Objective of the error and failure Handling is to have appropriate handling mechanism build in GeM Pool Account GPA would maintain a common error Library of the errors and every integrated bank will send the error code when that particular error or Failure occurs. The error code have been defined for all API and details of the specific error codes is available in the Integration document.

[Audio] Requirements from bank for Integration Bank Encryption Key : GeM is using AES 128 encryption for request and response encryption and decryption. Bank encryption key is used to encrypt/decrypt the request and response. Only Bank Encryption/Decryption keys of sizes 24 bit provided by bank as per GPA integration document. It should not contain special characters. Client token Key & Client token Value : For security purposes the bank needs to provide the Client token. It is sent with header for validating and accepting the request. It should not contain special characters. Challan URL : This is bank challan generation url, bank needs to provide this for generating challan. Bank IP to be white listed : Bank need to provide the IP address for white listing to GeM to allow request and response. Gem handles traffic at Port 443 so bank need to utilize network traffic on the same port. Bank Interface URL : This is the bank URL at which the GeM send the request using different endpoints as per the API document..

[Audio] Integration Plan The following Integration Plan would be adopted for integration of GeM and Banks Technical Integration document - Technical integration document is available on GeM Homepage. Banks can download the document from there Signoff of the Technical Integration document by Banks - Banks would signoff of the integration document thereby providing the consent to the services, workflow and data elements to be shared Completion of development and Unit Testing by the Bank - Bank would create new services and consume the GeM services and make required changes in their system and confirm the development completion to GeM Application testing of the integrated solution/ UAT Sign off - GeM would conduct the application level testing in collaboration with Bank technical team Production Release - Production deployment by Bank and GeM post Business and competent authority approval. Production Testing with One User - Bank would test in production with one user for whom the integration would be made available Business Go Live for all Users - This would make the feature available to all the users of the state.

[Audio] These are the Banks which are already integrated and enabled for GeM Pool account. The list includes banks from public as well as private sectors. With all these Banks the Standardized GPA solution is implemented and Buyers have opened accounts in these Banks to Operate GeM pool account for Procurements on GeM portal..

[Audio] Kindly Refer the GPA Technical design document for detailed integration mechanism and Api details. Thankyou.