mpesakit 0.1.2__tar.gz

mpesakit-0.1.2/.gitignore

@@ -0,0 +1,207 @@
+# ===== python.gitignore =====
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+#poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+#pdm.lock
+#pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+#pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Abstra
+# Abstra is an AI-powered process automation framework.
+# Ignore directories containing user credentials, local state, and settings.
+# Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#  and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#  you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+
+uv.lock

mpesakit-0.1.2/LICENSE

@@ -0,0 +1,73 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
+
+     (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
+
+     (b) You must cause any modified files to carry prominent notices stating that You changed the files; and
+
+     (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
+
+     (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
+
+     You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!)  The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
+
+Copyright 2025 John Kagunda
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

mpesakit-0.1.2/PKG-INFO

@@ -0,0 +1,226 @@
+Metadata-Version: 2.4
+Name: mpesakit
+Version: 0.1.2
+Summary: A Python SDK for integrating with M-Pesa APIs
+Project-URL: Homepage, https://github.com/rafaeljohn9/mpesakit
+Project-URL: Repository, https://github.com/rafaeljohn9/mpesakit
+Project-URL: Issues, https://github.com/rafaeljohn9/mpesakit/issues
+Author-email: John Kagunda <johnmkagunda@gmail.com>
+Maintainer-email: John Kagunda <johnmkagunda@gmail.com>
+License: APACHE-2.0
+License-File: LICENSE
+Keywords: africa,api,django,fastapi,flask,mobile money,mpesa,payment,payments,rest,sdk
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Internet :: WWW/HTTP :: Dynamic Content
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.12
+Requires-Dist: pydantic<3.0.0,>=2.10.6
+Requires-Dist: pydantic[email]<3.0.0,>=2.10.6
+Requires-Dist: requests<3.0.0,>=2.32.3
+Requires-Dist: typing-extensions<5.0.0,>=4.12.2
+Provides-Extra: dev
+Requires-Dist: bandit; extra == 'dev'
+Requires-Dist: build; extra == 'dev'
+Requires-Dist: coverage; extra == 'dev'
+Requires-Dist: hatch; extra == 'dev'
+Requires-Dist: hatch-vcs; extra == 'dev'
+Requires-Dist: hatchling; extra == 'dev'
+Requires-Dist: mypy; extra == 'dev'
+Requires-Dist: pytest; extra == 'dev'
+Requires-Dist: pytest-cov; extra == 'dev'
+Requires-Dist: ruff; extra == 'dev'
+Requires-Dist: types-requests; extra == 'dev'
+Provides-Extra: test
+Requires-Dist: bandit; extra == 'test'
+Requires-Dist: mypy; extra == 'test'
+Requires-Dist: pyngrok; extra == 'test'
+Requires-Dist: pytest; extra == 'test'
+Requires-Dist: pytest-cov; extra == 'test'
+Requires-Dist: types-requests; extra == 'test'
+Description-Content-Type: text/markdown
+
+# mpesa-daraja-sdk
+
+> ⚡ **Effortless M-Pesa integration** using Safaricom's Daraja API — built for developers, by developers.
+
+[![Python 3.12+](https://img.shields.io/badge/python-3.12+-blue.svg)](https://www.python.org/downloads/)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache%202.0-green.svg)](https://opensource.org/licenses/Apache-2.0)
+<!-- [![Build Status](https://img.shields.io/badge/build-passing-brightgreen.svg)]() -->
+
+---
+
+## The Problem
+
+Integrating Safaricom's **M-Pesa Daraja API** directly is **notoriously complex**:
+
+- Confusing and inconsistent documentation
+- Manual handling of OAuth2 tokens and security credentials
+- Complex encryption and certificate management
+- Different endpoints for sandbox vs production environments
+- STK Push, C2B, B2C, balance — all feel like separate APIs
+- Time-consuming setup that delays your time-to-market
+
+For many developers and startups, this becomes a **huge barrier** to adopting M-Pesa payments in Kenya and beyond.
+
+---
+
+## The Solution
+
+**`mpesa-daraja-sdk`** eliminates the complexity with a **clean, developer-friendly Python SDK** that:
+
+- **Zero-config setup** — just add your credentials and go
+- **Handles authentication automatically** — OAuth2, tokens, and security
+- **Seamless environment switching** — sandbox ↔ production with one parameter
+- **Pythonic interface** — clean methods that feel natural to Python developers
+- **Batteries included** — everything you need for M-Pesa integration
+- **Production-ready** — end goal is to be used by startups and enterprises across Kenya
+
+### Supported Features
+
+| Feature | Status | Description |
+|---------|--------|-------------|
+| **STK Push** | Ready | Lipa na M-Pesa Online payments |
+| **C2B Payments** | Ready | Customer to Business transactions |
+| **B2C Payments** | Ready | Business to Customer payouts |
+| **Token Management** | Ready | Automatic OAuth2 handling |
+| **Account Balance** | Coming Soon | Check account balances |
+|  **Transaction Reversal** | Coming Soon | Reverse transactions |
+| 🎣 **Webhook Validation** | Coming Soon | Secure callback handling |
+
+> Built on top of [Arlus/mpesa-py](https://github.com/Arlus/mpesa-py) with ❤️ — modernized, cleaned up, and restructured for today's developer needs.
+
+---
+
+## Quick Start
+
+### Installation (coming soon)
+
+```bash
+pip install mpesa-daraja-sdk
+```
+
+---
+
+## 📖 Complete Setup Guide
+
+### 1. Get Safaricom Developer Account
+
+1. Visit [developer.safaricom.co.ke](https://developer.safaricom.co.ke)
+2. **Create account** and verify your email
+3. **Create a new app** to get your credentials:
+   - Consumer Key
+   - Consumer Secret
+
+### 2. Obtain Test Credentials (Sandbox)
+
+1. Navigate to [Test Credentials Page](https://developer.safaricom.co.ke/test_credentials)
+2. Copy the following credentials:
+   - **Shortcode** (Business number)
+   - **Initiator Name** (API operator username)
+   - **Initiator Password** (API operator password)
+   - **Security Credential** (Encrypted password)
+
+### 3. Production Setup
+
+For production deployment:
+
+1. **Get Paybill/Till Number** from Safaricom
+2. **Generate Security Credential** using Safaricom's public certificate
+3. **Switch environment** to `"production"` in your client initialization
+4. **Update callback URLs** to your production domain
+
+---
+
+### Security Best Practices
+
+1. **Never commit credentials** to version control
+2. **Use environment variables** for sensitive data
+3. **Implement webhook validation** for callbacks
+4. **Log transactions** for audit trails
+5. **Monitor rate limits** and implement backoff strategies
+6. **Use HTTPS** for all callback URLs
+
+---
+
+## 🤝 Contributing
+
+We welcome contributions from the community! Here's how you can help:
+
+### Ways to Contribute
+
+- 🐛 **Report bugs** via GitHub Issues
+- 💡 **Suggest features** for the roadmap
+- 📖 **Improve documentation** and examples
+- 🔧 **Submit pull requests** with fixes/features
+- ⭐ **Star the repo** to show support
+
+### Development Setup
+
+```bash
+# Clone the repository
+git clone https://github.com/rafaeljohn9/mpesa-daraja-sdk.git
+cd mpesa-daraja-sdk
+
+# Create virtual environment
+python -m venv venv
+source venv/bin/activate  # On Windows: venv\Scripts\activate
+
+# Install in development mode
+pip install -e ".[dev]"
+
+# Run tests
+pytest tests/
+```
+
+### Code Standards
+
+- Follow PEP 8 style guidelines
+- Include type hints where appropriate
+- Write comprehensive tests for new features
+- Update documentation for any API changes
+
+---
+
+## 📞 Support & Community
+
+- 📖 **Documentation**: [Full API docs coming soon]
+- 🐛 **Issues**: [GitHub Issues](https://github.com/rafaeljohn9/mpesa-daraja-sdk/issues)
+- 💬 **Discussions**: [GitHub Discussions](https://github.com/rafaeljohn9/mpesa-daraja-sdk/discussions)
+- 📧 **Email**: <johnmkagunda@gmail.com>
+
+---
+
+## 🙏 Attribution & Thanks
+
+This project began as a fork of the fantastic [`Arlus/mpesa-py`](https://github.com/Arlus/mpesa-py) by [@Arlus](https://github.com/Arlus).
+
+**What we've added:**
+
+- 🏗️ **Modular architecture** for better maintainability
+- 🎯 **Developer-first design** with intuitive APIs
+- 🧪 **Comprehensive testing** suite
+- 📚 **Better documentation** and examples
+- 🚀 **Production-ready** features and error handling
+
+Special thanks to the original contributors and the broader Python community in Kenya.
+
+---
+
+## 📄 License
+
+Licensed under the [Apache 2.0 License](LICENSE) — free for commercial and private use.
+
+---
+
+<div align="center">
+
+**Made with ❤️ for the Kenyan developer community**
+
+[⭐ Star this repo](https://github.com/rafaeljohn9/mpesa-daraja-sdk) | [🐛 Report Issue](https://github.com/rafaeljohn9/mpesa-daraja-sdk/issues) | [💡 Request Feature](https://github.com/rafaeljohn9/mpesa-daraja-sdk/issues/new)
+
+</div>

mpesakit-0.1.2/README.md

@@ -0,0 +1,180 @@
+# mpesa-daraja-sdk
+
+> ⚡ **Effortless M-Pesa integration** using Safaricom's Daraja API — built for developers, by developers.
+
+[![Python 3.12+](https://img.shields.io/badge/python-3.12+-blue.svg)](https://www.python.org/downloads/)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache%202.0-green.svg)](https://opensource.org/licenses/Apache-2.0)
+<!-- [![Build Status](https://img.shields.io/badge/build-passing-brightgreen.svg)]() -->
+
+---
+
+## The Problem
+
+Integrating Safaricom's **M-Pesa Daraja API** directly is **notoriously complex**:
+
+- Confusing and inconsistent documentation
+- Manual handling of OAuth2 tokens and security credentials
+- Complex encryption and certificate management
+- Different endpoints for sandbox vs production environments
+- STK Push, C2B, B2C, balance — all feel like separate APIs
+- Time-consuming setup that delays your time-to-market
+
+For many developers and startups, this becomes a **huge barrier** to adopting M-Pesa payments in Kenya and beyond.
+
+---
+
+## The Solution
+
+**`mpesa-daraja-sdk`** eliminates the complexity with a **clean, developer-friendly Python SDK** that:
+
+- **Zero-config setup** — just add your credentials and go
+- **Handles authentication automatically** — OAuth2, tokens, and security
+- **Seamless environment switching** — sandbox ↔ production with one parameter
+- **Pythonic interface** — clean methods that feel natural to Python developers
+- **Batteries included** — everything you need for M-Pesa integration
+- **Production-ready** — end goal is to be used by startups and enterprises across Kenya
+
+### Supported Features
+
+| Feature | Status | Description |
+|---------|--------|-------------|
+| **STK Push** | Ready | Lipa na M-Pesa Online payments |
+| **C2B Payments** | Ready | Customer to Business transactions |
+| **B2C Payments** | Ready | Business to Customer payouts |
+| **Token Management** | Ready | Automatic OAuth2 handling |
+| **Account Balance** | Coming Soon | Check account balances |
+|  **Transaction Reversal** | Coming Soon | Reverse transactions |
+| 🎣 **Webhook Validation** | Coming Soon | Secure callback handling |
+
+> Built on top of [Arlus/mpesa-py](https://github.com/Arlus/mpesa-py) with ❤️ — modernized, cleaned up, and restructured for today's developer needs.
+
+---
+
+## Quick Start
+
+### Installation (coming soon)
+
+```bash
+pip install mpesa-daraja-sdk
+```
+
+---
+
+## 📖 Complete Setup Guide
+
+### 1. Get Safaricom Developer Account
+
+1. Visit [developer.safaricom.co.ke](https://developer.safaricom.co.ke)
+2. **Create account** and verify your email
+3. **Create a new app** to get your credentials:
+   - Consumer Key
+   - Consumer Secret
+
+### 2. Obtain Test Credentials (Sandbox)
+
+1. Navigate to [Test Credentials Page](https://developer.safaricom.co.ke/test_credentials)
+2. Copy the following credentials:
+   - **Shortcode** (Business number)
+   - **Initiator Name** (API operator username)
+   - **Initiator Password** (API operator password)
+   - **Security Credential** (Encrypted password)
+
+### 3. Production Setup
+
+For production deployment:
+
+1. **Get Paybill/Till Number** from Safaricom
+2. **Generate Security Credential** using Safaricom's public certificate
+3. **Switch environment** to `"production"` in your client initialization
+4. **Update callback URLs** to your production domain
+
+---
+
+### Security Best Practices
+
+1. **Never commit credentials** to version control
+2. **Use environment variables** for sensitive data
+3. **Implement webhook validation** for callbacks
+4. **Log transactions** for audit trails
+5. **Monitor rate limits** and implement backoff strategies
+6. **Use HTTPS** for all callback URLs
+
+---
+
+## 🤝 Contributing
+
+We welcome contributions from the community! Here's how you can help:
+
+### Ways to Contribute
+
+- 🐛 **Report bugs** via GitHub Issues
+- 💡 **Suggest features** for the roadmap
+- 📖 **Improve documentation** and examples
+- 🔧 **Submit pull requests** with fixes/features
+- ⭐ **Star the repo** to show support
+
+### Development Setup
+
+```bash
+# Clone the repository
+git clone https://github.com/rafaeljohn9/mpesa-daraja-sdk.git
+cd mpesa-daraja-sdk
+
+# Create virtual environment
+python -m venv venv
+source venv/bin/activate  # On Windows: venv\Scripts\activate
+
+# Install in development mode
+pip install -e ".[dev]"
+
+# Run tests
+pytest tests/
+```
+
+### Code Standards
+
+- Follow PEP 8 style guidelines
+- Include type hints where appropriate
+- Write comprehensive tests for new features
+- Update documentation for any API changes
+
+---
+
+## 📞 Support & Community
+
+- 📖 **Documentation**: [Full API docs coming soon]
+- 🐛 **Issues**: [GitHub Issues](https://github.com/rafaeljohn9/mpesa-daraja-sdk/issues)
+- 💬 **Discussions**: [GitHub Discussions](https://github.com/rafaeljohn9/mpesa-daraja-sdk/discussions)
+- 📧 **Email**: <johnmkagunda@gmail.com>
+
+---
+
+## 🙏 Attribution & Thanks
+
+This project began as a fork of the fantastic [`Arlus/mpesa-py`](https://github.com/Arlus/mpesa-py) by [@Arlus](https://github.com/Arlus).
+
+**What we've added:**
+
+- 🏗️ **Modular architecture** for better maintainability
+- 🎯 **Developer-first design** with intuitive APIs
+- 🧪 **Comprehensive testing** suite
+- 📚 **Better documentation** and examples
+- 🚀 **Production-ready** features and error handling
+
+Special thanks to the original contributors and the broader Python community in Kenya.
+
+---
+
+## 📄 License
+
+Licensed under the [Apache 2.0 License](LICENSE) — free for commercial and private use.
+
+---
+
+<div align="center">
+
+**Made with ❤️ for the Kenyan developer community**
+
+[⭐ Star this repo](https://github.com/rafaeljohn9/mpesa-daraja-sdk) | [🐛 Report Issue](https://github.com/rafaeljohn9/mpesa-daraja-sdk/issues) | [💡 Request Feature](https://github.com/rafaeljohn9/mpesa-daraja-sdk/issues/new)
+
+</div>