Developer Docs
API Endpoints
Eko.inGithubAsk GPT

AePS API

AePS API act as Cash-out service. It has three main components.

  • Aadhaar (aadhaar number should be sent encrypted)
  • Biometric information (fingerprint data)

❗️

Note

Only IP which is in India will be whitelisted while going on the production mode. IP which is present outside India will not be whitelisted as per compliance.

Process Flow -

  1. Onboard the retailer with the correct details using Onboard User API .
  2. Proceed to activate the service for the user_code of the retailer using the Activate Service (AePS) API.
  3. Perform the merchant's e-KYC using FINGPAY. To do e-KYC through FINGPAY, you will need to call the following APIs consecutively:
    e-KYC OTP Request (API: https://developers.eko.in/reference/e-kyc-otp-request)
     e-KYC OTP Verification (API: https://developers.eko.in/reference/e-kyc-otp-verification)
    * e-KYC using Biometric (API: https://developers.eko.in/reference/e-kyc-using-biometric)
  4. ⁠After successfully hitting these three APIs, the e-KYC process through FINGPAY will be completed.
  5. For FINO, or service_code = 52, after AePS activation, use only e-KYC using biometric.
  6. After the merchant's e-KYC is complete, you need to perform Daily Authentication using the AEPS Daily Authentications API (API: https://developers.eko.in/reference/aeps-daily-authentications).
  7. After daily authentication, use merchant authentication to authenticate the merchant before every transaction. (applicable from 1st JAN, 24)
  8. Once the merchant has completed the Daily e-KYC and merchant authentication, they can proceed to perform a transaction.

📘

Public key for aadhar encryption (PRODUCTION) -

MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCaFyrzeDhMaFLx+LZUNOOO14Pj9aPfr+1WOanDgDHxo9NekENYcWUftM9Y17ul2pXr3bqw0GCh4uxNoTQ5cTH4buI42LI8ibMaf7Kppq9MzdzI9/7pOffgdSn+P8J64CJAk3VrVswVgfy8lABt7fL8R6XReI9x8ewwKHhCRTwBgQIDAQAB