Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Introduction
| align | justify |
|---|
Before you actually get started with
Zeta paymentPWZ functionality, you will need
to createa Zeta
Merchantdeveloper account to gain access to various
server- and client-side Pay with Zeta SDKs andPWZ RESTful APIs and related methods. These
SDK integrations into your existing projectAPIs will help you to enable accepting payments from Zeta users instantly over a secured network.
CreatingProvisioning a
Merchant accountThis involves giving basic details of your business (name, contact details, ), bank account details for receiving settlement and specifying you nature of business aka AMC (Authorized Merchant Code) to allow Zeta to determine from which instrument zeta users can pay you.
You need to create a new Zeta account on your mobile device to get started with Zeta digital platform. Corporate HR issues virtual corporate benefit cards to your account and you are notified to your registered mobile number or via official email. Download, install and configure the Zeta app to gain access to the Zeta app features.
What You Get
When you create a Zeta merchant account, a Merchant ID will be assigned that you specify during the sign up processDeveloper Account
| Note |
|---|
Zeta merchant on-boarding/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 the PWZ APIs. 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 |
| pass 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 Establish secure HTTPS URL endpoints to redirect users to Zeta payment gateway from your web site and vice versa.
- Integrate PWZ using the Checkout Flow, Save Source Flow and App2App Flow.
| Panel | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| pista
| title
| This Page
|