Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Introduction
Before you actually get started with Zeta payment functionality, you need to create a Zeta Merchant account to gain access to various server- and client-side Pay with Zeta SDKs and related methods. These SDK integrations into your existing project help you to enable accepting payments from Zeta users instantly over a secured network.
Creating a Merchant's Developer Account
Note |
---|
Zeta merchant onboarding/sales team will assist you to create a new Zeta merchant account. |
You would To request for a developer account, you need to provide your business details such as:
- Merchant company name: A company is a legal entity required to open a developer account and also for the compliance.
- Contact details: An official mobile number of the contact person. This is needed to link to the developer account
- Bank account details: Bank details are mandatory to receive payment from Zeta users and resolve payment settlement.
- Authorized merchant code (AMC): This is mandatory if you use an EDC machine to receive payments. With AMC, Zeta will identify your nature of business and then determine the user's digital instrument type to release the payment to you (merchant) as requested. For example, if you run a medicine shop, Zeta will ensure that you receive the payment from user's digital medical card.
Zeta then verifies the relevant details and co-ordinates you in case of invalid entries and documents. Upon successful verification, Zeta approves the request and delegates you a developer account.
What You Receive
When you create a Zeta merchant account, a Merchant ID will be assigned that you specify during the sign up process. You receive the following with your active account that you will use to trigger secure API calls to Zeta payment gateway.
Merchant Entity | Description |
---|---|
Merchant ID | A unique ID provisioned to each merchant signed up with Zeta |
Merchant Signatory ID | A unique signatory ID associated with every merchant |
Private and Public Key | Keys for signing the requests |
Zeta Public Key | Validates asynchronous responses from Zeta |
API Auth Token | An authorization token required to passed in API request headers |
Next Steps
- Download and install a server-side or client-side SDK that suits your development environment and as per organization's e-commerce payment model - web or mobile. To download Zeta SDKs, see Download SDKs.
- Ensure to use secure HTTPS URL endpoints to redirect users to Zeta payment gateway from your web site and vice versa.
Panel | ||||||
---|---|---|---|---|---|---|
|