Developers

Developers

Build on DzWallet

Official libraries, plugins and API files to accept payments in minutes. Start in test mode, go live when you are ready.

composer require dzwallet/laravel-sdk
use DzWallet\Facades\DzWallet;

// Set DZWALLET_MODE=test and configure your test keys in .env.
// Add the dzwallet.ipn route from the API documentation.
$payment = DzWallet::initiatePayment([
    'identifier'  => $order->identifier,
    'amount'      => $order->total,
    'details'     => 'Order #' . $order->id,
    'ipn_url'     => route('dzwallet.ipn'),
    'success_url' => route('thanks'),
    'cancel_url'  => route('cart'),
    'site_name'   => 'My shop',
    'customer'    => $customer,   // first_name, last_name, email, mobile
]);

return redirect()->away($payment->redirectUrl);

Quick start

  1. Copy your test keys from the merchant dashboard and register your callback and redirect domains.
  2. Install a library below, or call the API directly.
  3. Create a SATIM payment in DZD on your server. Redirect the customer after the API returns a successful checkout.
  4. Confirm the order with the signed notification or a server-side status check.

Libraries and plugins

Laravel

Available

Official package for Laravel 10, 11 and 12: payments, signed IPN route, events.

composer require dzwallet/laravel-sdk

PHP

Available

Plain PHP 7.4+ client, no framework needed.

composer require dzwallet/php-sdk

Node.js

Available

Node 18+ client with TypeScript types and an Express example.

npm install dzwallet-node

Python

Available

Python 3.8+ client for Django, Flask and FastAPI.

pip install dzwallet
In testing

Flutter

Checkout page and payment status checker for mobile apps. The secret key stays on your server.

WooCommerce

WordPress plugin: DzWallet appears as a payment method at checkout.

PrestaShop

PrestaShop module with signed IPN and order confirmation.

API files

OpenAPI 3.1Merchant payment endpoints and signed notifications for Swagger, Insomnia or your code generator.
openapi.yaml
PostmanTest and live payment requests. Payment links require live keys.
Postman

Security rules

  • Keep your secret key on your server only. Never put it in a mobile app, a web page or a public repository.
  • Do not trust the success page redirect. Confirm with the signed IPN or a server side status check.
  • Match the identifier, amount and currency to your order. Record each signed notification event ID once.
  • If a payment request times out, check its status before creating another checkout.
  • With direct API calls, HTTP 200 can contain an application error. Read the JSON status before using the checkout URL or payment status.

We may use cookies or any other tracking technologies when you visit our website, including any other media form, mobile website, or mobile application related or connected to help customize the Site and improve your experience. learn more

Allow