Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
align

Introduction

alignjustify

Before you actually get started with

Zeta payment

PWZ functionality, you will need

to create

a Zeta

Merchant

developer account to gain access to various

server- and client-side Pay with Zeta SDKs. These SDK integrations into your existing project

PWZ 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 program

Provisioning 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

Optima

merchant 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 merchant 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

  • 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. Zeta 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.
  • Ensure to use

    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 EntityDescription
    Merchant IDA unique ID provisioned to each merchant signed up with Zeta
    Merchant Signatory IDA unique signatory ID associated with every merchant
    Private and Public KeyKeys for signing the requests
    Zeta Public KeyValidates asynchronous responses from Zeta
    API Auth TokenAn authorization token required to pass in API request headers

    Next Steps

    1. Establish secure HTTPS URL endpoints to redirect users back to your website from Zeta payment gateway from your web site and vice versa.
    2. Integrate PWZ using the Checkout FlowSave Source Flow and App2App Flow.


    bgColorpistatitle This Page
    Panel


    Div
    class
    alignLeftIcon

    On

    Table of Contents

    Related pages

    Content by Label
    showLabelsfalse
    spacesPWZ
    showSpacefalse
    sorttitle
    typepage
    cqllabel = "documentation-space-sample" and type = "page" and space = "PWZ"
    labelsdocumentation-space-sample

    Info
    titleUseful hint

    Confluence Administrators can also make templates that are available across your whole Confluence instance.

    this page:

    Table of Contents