From 05d3ba794bdd1b044fcd72ee5dd240b712c4c998 Mon Sep 17 00:00:00 2001 From: S4NKALP Date: Thu, 3 Sep 2026 00:57:32 +0545 Subject: [PATCH] docs: add badges and drop contents section --- README.md | 38 ++++++++++++++++++++++---------------- 1 file changed, 22 insertions(+), 16 deletions(-) diff --git a/README.md b/README.md index b51bdbb..58c5b9b 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,27 @@ # django-nepali-payment +

+ + CI + + + PyPI version + + + Python versions + + Django + + PyPI downloads + + + License + + + Last commit + +

+ Accept payments in Nepal from your Django app with a single, consistent API. We handle **Khalti**, **eSewa**, **Fonepay** (Dynamic QR, Static QR, status @@ -21,22 +43,6 @@ uv add django-nepali-payment specific Django major). It bundles `requests` for transport and `cryptography` for ConnectIPS RSA signing. -### Contents - -- [What you get](#what-you-get) -- [How it's built](#how-its-built) -- [Quick start](#quick-start) · [Tune the HTTP client](#tuning-the-http-client) -- [Initiate a payment](#initiate-a-payment) — eSewa, Khalti, Fonepay -- [Fonepay Static QR](#fonepay-static-qr) -- [ConnectIPS](#connectips) -- [Verify a payment](#verify-a-payment) -- [Errors](#errors) · [Handling callbacks safely](#handling-callbacks-safely) -- [Fonepay QR status monitoring](#fonepay-qr-status-monitoring) -- [Why polling](#why-polling-instead-of-websockets) -- [See it in action](#see-it-in-action) · [Development](#development) · [CI](#ci) - ---- - ## What you get - **One shape for every gateway.** Every call returns a `PaymentResult`, so