Developer Reference
Page tree

Versions Compared

Old Version 2

changes.mady.by.user Super Admin

Saved on

compared with

New Version Current

changes.mady.by.user user-8f2bd

Saved on

Key

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

Give your authors a helping hand by using templates in your documentation space. You will need Space Administrator permissions to create templates.

To create a template:

  1. Go to "Space Tools" in the sidebar, select "Content Tools" and create a new template.
  2. Click "Page Layout" and add sections and columns to your page.
  3. Add headings and sub-headings as needed.
  4. Choose "Instructional Text" from the "Template" menu and add text that is only visible in the editor.
  5. Save your template.

Your template will become available in the Create dialog for this space.

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.

Introduction

Before you actually get started with PWZ functionality, you will need a Zeta developer account to gain access to various PWZ RESTful APIs and related methods. These APIs will help you to enable accepting payments from Zeta users instantly over a secured network.

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 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 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 to Zeta payment gateway from your web site and vice versa.
  2. Integrate PWZ using the Checkout Flow, Save Source Flow and App2App Flow.


Panel


Div
classalignLeftIcon

On this page:

Table of Contents