django-hesabpay
Beginner-friendly Django SDK for the HesabPay Payment Gateway.
Start a hosted checkout with hesabpay.checkout(...), then run your business logic in @on_payment_success. Redirects are for UX. Verified webhooks are the source of truth.
Install
pip install django-hesabpay
Requires Python 3.10+ and Django 4.2+.
Quickstart
1. Settings
# settings.py
INSTALLED_APPS = [
# ...
"hesabpay",
]
HESABPAY = {
"ENVIRONMENT": "sandbox", # or "production"
"SANDBOX_API_KEY": "your-sandbox-key",
# "PRODUCTION_API_KEY": "your-live-key", # when ENVIRONMENT=production
"HANDLERS": ["shop.payments"], # modules that register @on_payment_success
}
2. Migrate
python manage.py migrate
Webhook and status routes register automatically. The default webhook path is /hesabpay/webhook/. Copy that URL into the HesabPay dashboard.
3. Start checkout
import hesabpay
from django.shortcuts import redirect
def pay(request, order):
checkout = hesabpay.checkout(order, user=request.user)
return redirect(checkout.url)
Or from a template:
{% load hesabpay %}
{% hesabpay_checkout_button order user=request.user %}
JSON APIs can return checkout.as_dict() with payment_id, checkout_url, status, and items.
4. Fulfill after payment
# shop/payments.py
from hesabpay import on_payment_success
@on_payment_success
def fulfill(context):
# Your product decides: enroll, unlock, email, ship, etc.
order = context.instance
user = context.user
items = context.items # local HesabPayPaymentItem rows
webhook_items = context.webhook_items # items list from HesabPay webhook
if not context.is_first_success:
return
...
HesabPay webhooks include an items array (same shape as create-session). The SDK stores those line items locally and exposes them on the payment context and status endpoint.
Amounts are AFN. Currency conversion is out of scope for v1.
Multi-vendor (advanced)
After a payment succeeds, settle vendors with an encrypted PIN (documented HesabPay API):
from hesabpay import transfer_to_vendors
transfer_to_vendors(
payment=payment,
vendors=[{"account_number": "700000001", "amount": 50}],
pin="1234",
)
Auto-settle is off by default (AUTO_VENDOR_TRANSFER).
Commands
python manage.py hesabpay doctor
python manage.py hesabpay simulate-webhook <payment_reference>
Django admin includes payments, webhook events, vendor payouts, and activity logs. Use Replay fulfillment handlers on a webhook event if a handler failed after the payment was already acknowledged.
Official API docs
Metadata
Release files for django-hesabpay 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django_hesabpay-0.1.3.tar.gz | 23.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_hesabpay-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.5 kB
Release files / django_hesabpay-0.1.3.tar.gz
| Download URL | django_hesabpay-0.1.3.tar.gz |
|---|---|
| Size | 23.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
afb7f2673a7def0de7cf546de67bc8df606d042a18261e04f55260abbf34d1e2
|
|
BLAKE2b-256 checksum How to use checksums |
0f76d1d0b97e5cd337018315c8ddb407cc498fca0831ccaa7556c6d1cb0e367d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 4, 2026.
Transparency logRelease files / django_hesabpay-0.1.3-py3-none-any.whl
| Download URL | django_hesabpay-0.1.3-py3-none-any.whl |
|---|---|
| Size | 30.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
78e5cb2e24f9b8f8910ae33c281a682c4e8943c230f302591da2af848e8ab1bb
|
|
BLAKE2b-256 checksum How to use checksums |
932d7a3b8cc1ef3527bc130c2967d75b5f5923ce2fd6d53662a54424b06a68c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 4, 2026.
Transparency log