This process activates a service for a user using shop_type from the Get MCC Category API and state_id from the Get States API.
Mandatory Parameters for AePS activation :
For the AePS API activation, you need to pass user_code, initiator_id, service_code = 43, modelname, devicenumber, office_address, address_as_per_proof, pan_card as mandatory and aadhar_front and aadhar_back.
Make sure that you enter correct modelname and devicenumber. Do not do testing with your production credentials
If you are integrating AePS Gateway solution then activate the service using service_code as 43 .
By activating AePS API service for merchants using the service code = 43, they will be able to conduct AePS. If we find any mismatch in documents, the merchant’s AePS business will be paused. We will communicate the same to you within 24 working hours of merchant activation and ask for re-uploading updated documents. Post re-upload, the status will go in PENDING state and waiting for the action to be taken by the OPS team.
AePS Activation TAT
For AePS API - After activation, the user state goes into pending state and it will take 2-3 business day for any user to get onboarded on fingpay .
Please Note:
- Please use correct and clear images, as these are checked in the back-end and your service will be deactivated if the images are incorrect or not in the correct format.
- The file size for the documents for AePS activation should be less than 1MB.
- We accept the images in JPEG, JPG, and PDF format, not in PNG. PNG images are rejected from the partner bank.
- Make sure you're passing the correct device number and model name for the BIOMETRIC device that you're using.
- The withdrawal amount for AEPS transactions must strictly adhere to being in multiples of 50 or 100, ensuring compliance with standard banking guidelines.
- The AEPS transaction limit for a merchant is ₹10,000 for all transactions combined within a one-week period.