ZionPe for developers

One API call to a hosted checkout

Create a session, send the customer to the checkout URL, hear back on a signed webhook. Node.js and PHP libraries, a sandbox that mirrors production, and docs written by the people who run the API.

Base URL zionpe.com/api HMAC-signed requests and webhooks Sandbox included
server.js · npm install zionpe

Small surface, no surprises

Amounts in major units, JSON in and out, one signing scheme everywhere.

Hosted checkout in one call

Create a checkout session from your server, redirect to the checkout URL, done. Cards, Apple Pay and Google Pay on a page ZionPe keeps compliant.

Signed requests

A public Site Key identifies you; a private Site Secret signs every request with an HMAC of the exact body. Nobody can move money with a public key.

Signed webhooks

Payment completed, refunded, disputed and more, delivered with a signature you verify in one line. Retries until you return 200.

Sandbox that mirrors live

A separate sandbox Site Key. Same code, same endpoints, test cards only. Flip the key to go live.

Idempotent by design

Send an Idempotency-Key and a retry returns the original session instead of creating a second charge.

Clear errors, fast answers

Every failure returns a code and a plain-English message that says what to fix. POST /api/checkout/ping verifies your signature in seconds.

Client libraries

Node.js

ESM and CommonJS, zero dependencies
npm install zionpe

PHP / Laravel

PHP 7.4+, zero dependencies
composer require zionpe/zionpe-php

Any language

Twelve lines, reference code in the docs
HMAC-SHA256 over the raw body

Signed requests are required for every account from 5 October 2026. The libraries sign for you; the docs carry the reference implementation if you roll your own.

Frequently asked questions

What does the ZionPe Checkout API do?

Your server creates a checkout session with one signed POST, you send the customer to the returned checkout URL, and a webhook tells you when they paid. Refunds and session lookups are signed calls too.

Is there a client library?

Yes. "zionpe" on npm for Node.js and "zionpe/zionpe-php" on Packagist for PHP and Laravel. Both have no dependencies and handle request signing and webhook verification for you.

How is the API secured?

Every account has a public Site Key and a private Site Secret. Requests are signed with an HMAC of the exact body. Signed requests are required for everyone from 5 October 2026.

Can I test without charging a real card?

Yes. Developers → Sandbox gives you a separate sandbox Site Key. The same code runs against sandbox in development and live in production; only the key changes.

What about the Billing and Commerce APIs?

ZionPe Billing has its own API and webhooks for customers, plans, subscriptions and invoices, documented at docs.zionpe.com/billing. ZionPe Commerce needs no API; it works through Shopify's own subscription contracts.

Ship a checkout this afternoon

Sign up, grab sandbox keys from Developers → Sandbox, and make your first signed call. API access is included in Payments Pro.