Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Introduction
Before you actually get started with PWZ functionality, you will need to provision a Zeta developer account to gain access to various server- and client-side PWZ 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.
Provisioning a Developer Account
Note |
---|
Zeta merchant onboarding/sales team will assist you to provision a new Zeta developer account. |
When you create a Zeta merchant account, Zeta will provision a developer account that allows you to access or integrate the PWZ SDKs. This also enables you to securely communicate with Zeta payment server and invoke API requests.
What You Receive
Once your developer account is provisioned, you will be assigned a unique Merchant ID. You receive the following with your active developer 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 | ||||||
---|---|---|---|---|---|---|
|