django-payments-payzum

Accept crypto and stablecoin payments (USDC, USDT and more, multi-chain) in any django-payments project through Payzum — non-custodial: funds settle directly to your own wallet, Payzum never takes custody.

How it works

1. The buyer picks Payzum at checkout and is redirected to a hosted checkout page, where they choose the asset and chain and send the payment. No wallet data touches your server.
2. Crypto confirmation is asynchronous, so the payment is confirmed from Payzum's signed server-to-server notification, never from the browser return. A buyer who comes back while the payment is still confirming lands on your success page with the payment in waiting — the signed notification flips it to confirmed.
3. Every notification is verified with HMAC-SHA-512 over the raw request bytes (with a replay window) before a single field of it is read, and the invoice amount and currency are re-checked against the payment before it is confirmed. Redelivered notifications are a no-op, so an order is never fulfilled twice.

Installation

pip install django-payments-payzum

Add the provider to your PAYMENT_VARIANTS:

PAYMENT_VARIANTS = {
    "payzum": ("payments_payzum.PayzumProvider", {
        "api_key": "...",           # merchant.payzum.com → Settings → API Keys
        "webhook_secret": "...",    # shown once, at merchant creation or rotation
        "endpoint": "production",   # or "sandbox" (staging, separate API keys)
        "pay_currency": "all",      # or pin one asset, e.g. "usdcmatic"
    }),
}

Keep both keys out of source control (environment variables or your secret store), like any other payment credential.

There is nothing to configure in the Payzum dashboard: the notification URL (django-payments' own process/<token>/ route) is sent with every invoice. The static process/payzum/ route also works — the payment is resolved from the signed payload only.

Status mapping

Tests

pip install -e . pytest pytest-django
pytest

License

MIT. The payzum SDK it builds on is MIT as well.