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. These SDK integrations into your existing projectPWZ RESTful APIs and related methods. These APIs will help you to enable accepting payments from Zeta users instantly over a secured network.
corporate benefit programsZeta recommends you to quickly go through the Funding Accounts and Administration menus to manage your fund accounts and corporate entities. Ensure to keep sufficient funds in your funding accounts to initiate an employee transfer through a benefit programProvisioning a Developer Account
| Note |
|---|
Zeta merchant on-boarding/sales team will assist you to provision a new Zeta developer account. |
When you create a Zeta
Optimamerchant account,
a company will be provisioned for you that you specify during the sign up process. A company is a legal entity and serves as a container for your benefit programs including the employees you transfer the benefits to. Under a company you can create a new benefit program such as medical, meal, communication and/or process an employee transfer using the active program.You need to create a new Zeta HR account to gain access to various corporate benefit programs, for example, meal vouchers, medical reimbursements, communication reimbursements, fuel reimbursements, LTA, gift cards and incentives
This involves giving basic details of your business (name, contact details, etc.), 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.
Creating a Merchant account
This involves giving basic details of your business (name, contact details, etc.), 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.
- Merchant ID
- Merchant Signatory ID
- Private key & Public Key (will be used for signing requests)
- Zeta Public Key (will be used to validate asynchronous responses from Zeta)
- API Auth Token (Needs to passed in API request headers)
Your template will become available in the Create dialog for this space.
What You Get
When you create a Zeta Optima account, a company will be provisioned for you that you specify during the sign up process. A company is a legal entity and serves as a container for your benefit programs including the employees you transfer the benefits to. Under a company you can create a new benefit program such as medical, meal, communication and/or process an employee transfer using the active program.
Once signed up, you should receive the following:
- Merchant ID
- Merchant Signatory ID
- Private key & Public Key (will be used for signing requests)
- Zeta Public Key (will be used to validate asynchronous responses from Zeta)
- API Auth Token (Needs to passed in API request headers)
Next Steps
You will need the Server-Side and client-side SDKs that take care of the cryptography required for making API calls to Zeta and other related function . We have libraries for all popular programming languages.
You will need to provide secure (HTTPS) URL endpoints that will be used for redirecting users back to your website.
| Panel | ||||
|---|---|---|---|---|
| ||||
|
Related pages
| Content by Label | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Info | ||
|---|---|---|
| ||
Confluence Administrators can also make templates that are available across your whole Confluence instance. |
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
- 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 | ||||||
|---|---|---|---|---|---|---|
|