python-getpaid-payu 0.1.0__tar.gz

python_getpaid_payu-0.1.0/.gitignore

@@ -0,0 +1,20 @@
+# Python-generated files
+__pycache__/
+*.py[oc]
+build/
+dist/
+wheels/
+*.egg-info
+
+# Virtual environments
+.venv
+
+# Coverage
+.coverage
+htmlcov/
+
+# Implementation plans (local only)
+.plans/
+
+# Sphinx build output
+docs/_build/

python_getpaid_payu-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,15 @@
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v5.0.0
+    hooks:
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: check-yaml
+      - id: check-added-large-files
+
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.11.12
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format

python_getpaid_payu-0.1.0/.python-version

@@ -0,0 +1 @@
+3.12

python_getpaid_payu-0.1.0/.readthedocs.yml

@@ -0,0 +1,12 @@
+version: 2
+build:
+  os: ubuntu-24.04
+  tools:
+    python: "3.12"
+sphinx:
+  configuration: docs/conf.py
+formats: all
+python:
+  install:
+    - requirements: docs/requirements.txt
+    - path: .

python_getpaid_payu-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[dominik@kozaczko.info](mailto:dominik@kozaczko.info).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][mozilla coc].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][faq]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[mozilla coc]: https://github.com/mozilla/diversity
+[faq]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

python_getpaid_payu-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,61 @@
+# Contributor Guide
+
+Thank you for your interest in improving getpaid-payu.
+This project is open-source under the [MIT license](https://github.com/django-getpaid/python-getpaid-payu/blob/main/LICENSE) and
+welcomes contributions in the form of bug reports, feature requests, and pull requests.
+
+## Resources
+
+- [Source Code](https://github.com/django-getpaid/python-getpaid-payu)
+- [Documentation](https://getpaid-payu.readthedocs.io/)
+- [Issue Tracker](https://github.com/django-getpaid/python-getpaid-payu/issues)
+
+## How to report a bug
+
+Report bugs on the [Issue Tracker](https://github.com/django-getpaid/python-getpaid-payu/issues).
+
+When filing an issue, include:
+
+- Operating system and Python version
+- getpaid-payu version
+- Steps to reproduce
+- Expected vs actual behavior
+
+## How to set up your development environment
+
+You need Python 3.12+ and [uv](https://docs.astral.sh/uv/).
+
+Clone and install:
+
+```bash
+git clone https://github.com/django-getpaid/python-getpaid-payu.git
+cd python-getpaid-payu
+uv sync
+```
+
+Run tests:
+
+```bash
+uv run pytest
+```
+
+Run linting:
+
+```bash
+uv run ruff check src/ tests/
+uv run ruff format --check src/ tests/
+```
+
+## How to submit changes
+
+1. Fork the repository and create a feature branch
+2. Write tests for your changes
+3. Ensure all tests pass: `uv run pytest`
+4. Ensure linting passes: `uv run ruff check src/ tests/`
+5. Open a pull request
+
+Your pull request needs to:
+
+- Pass the test suite without errors
+- Include tests for new functionality
+- Update documentation if adding features

python_getpaid_payu-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2022-2026 Dominik Kozaczko
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

python_getpaid_payu-0.1.0/PKG-INFO

@@ -0,0 +1,152 @@
+Metadata-Version: 2.4
+Name: python-getpaid-payu
+Version: 0.1.0
+Summary: PayU payment gateway integration for python-getpaid ecosystem.
+Project-URL: Homepage, https://github.com/django-getpaid/python-getpaid-payu
+Project-URL: Repository, https://github.com/django-getpaid/python-getpaid-payu
+Project-URL: Documentation, https://getpaid-payu.readthedocs.io/
+Project-URL: Changelog, https://github.com/django-getpaid/python-getpaid-payu/releases
+Author-email: Dominik Kozaczko <dominik@kozaczko.info>
+License: MIT
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Office/Business :: Financial
+Classifier: Topic :: Office/Business :: Financial :: Point-Of-Sale
+Classifier: Typing :: Typed
+Requires-Python: >=3.12
+Requires-Dist: httpx>=0.27.0
+Requires-Dist: python-getpaid-core>=0.1.0
+Description-Content-Type: text/markdown
+
+# getpaid-payu
+
+[![PyPI](https://img.shields.io/pypi/v/python-getpaid-payu.svg)](https://pypi.org/project/python-getpaid-payu/)
+[![Python Version](https://img.shields.io/pypi/pyversions/python-getpaid-payu)](https://pypi.org/project/python-getpaid-payu/)
+[![License](https://img.shields.io/pypi/l/python-getpaid-payu)](https://github.com/django-getpaid/python-getpaid-payu/blob/main/LICENSE)
+
+PayU payment gateway plugin for the
+[python-getpaid](https://github.com/django-getpaid) ecosystem. Provides a
+fully async HTTP client (`PayUClient`) and a payment processor
+(`PayUProcessor`) implementing the
+[getpaid-core](https://github.com/django-getpaid/python-getpaid-core)
+`BaseProcessor` interface. Communicates with PayU via their REST API v2.1
+using OAuth2 authentication.
+
+## Architecture
+
+getpaid-payu is composed of two main layers:
+
+- **PayUClient** — a low-level async HTTP client (built on `httpx`) that wraps
+  every PayU REST API v2.1 endpoint. OAuth2 tokens are obtained lazily and
+  refreshed automatically. Can be used as an async context manager for
+  connection reuse.
+- **PayUProcessor** — a high-level processor that implements `BaseProcessor`
+  from getpaid-core. Translates between the core payment protocol and PayU's
+  API, handles signature verification, PUSH/PULL callbacks, and FSM
+  transitions.
+
+## Key Features
+
+- Full PayU REST API v2.1 coverage
+- Async HTTP client with automatic OAuth2 token management
+- Create order, cancel, capture (charge), retrieve order info
+- Refund operations: create, retrieve single, retrieve all
+- Payment methods retrieval
+- Transaction details retrieval
+- Shop info and payout operations
+- Token deletion (card-on-file)
+- Automatic amount centification (amounts × 100) and normalization
+- Signature verification (MD5 and SHA-256)
+- PUSH callback handling with FSM integration
+- PULL status polling
+- Full pre-authorization support (lock, charge, release)
+
+## Quick Usage
+
+`PayUClient` can be used standalone as an async context manager:
+
+```python
+from decimal import Decimal
+from getpaid_payu.client import PayUClient
+from getpaid_payu.types import Currency
+
+async with PayUClient(
+    api_url="https://secure.snd.payu.com/",
+    pos_id=300746,
+    second_key="b6ca15b0d1020e8094f2b...",
+    oauth_id=300746,
+    oauth_secret="2ee86a66e5d97e3fadc4...",
+) as client:
+    response = await client.new_order(
+        amount=Decimal("29.99"),
+        currency=Currency.PLN,
+        order_id="order-123",
+        description="Test order",
+    )
+    redirect_url = response["redirectUri"]
+```
+
+## Configuration
+
+When used via a framework adapter (e.g. django-getpaid), configuration is
+provided as a dictionary:
+
+| Key | Type | Default | Description |
+|-----|------|---------|-------------|
+| `pos_id` | `int` | — | PayU POS (point of sale) identifier |
+| `second_key` | `str` | — | Second key (MD5) from PayU panel, used for signature verification |
+| `oauth_id` | `int` | — | OAuth client ID from PayU panel |
+| `oauth_secret` | `str` | — | OAuth client secret from PayU panel |
+| `sandbox` | `bool` | `True` | Use sandbox (`secure.snd.payu.com`) or production (`secure.payu.com`) |
+| `notify_url` | `str` | `None` | Notification callback URL template, e.g. `https://example.com/payments/{payment_id}/notify` |
+| `continue_url` | `str` | `None` | Redirect URL template after payment, e.g. `https://example.com/payments/{payment_id}/continue` |
+
+Example configuration dict:
+
+```python
+GETPAID_BACKENDS = {
+    "payu": {
+        "pos_id": 300746,
+        "second_key": "b6ca15b0d1020e8094f2b...",
+        "oauth_id": 300746,
+        "oauth_secret": "2ee86a66e5d97e3fadc4...",
+        "sandbox": True,
+        "notify_url": "https://example.com/payments/{payment_id}/notify",
+        "continue_url": "https://example.com/payments/{payment_id}/continue",
+    }
+}
+```
+
+## Supported Currencies
+
+BGN, CHF, CZK, DKK, EUR, GBP, HRK, HUF, NOK, PLN, RON, RUB, SEK, UAH, USD
+
+## Requirements
+
+- Python 3.12+
+- `python-getpaid-core >= 0.1.0`
+- `httpx >= 0.27.0`
+
+## Related Projects
+
+- [getpaid-core](https://github.com/django-getpaid/python-getpaid-core) —
+  framework-agnostic payment processing library
+- [django-getpaid](https://github.com/django-getpaid/django-getpaid) —
+  Django framework adapter
+
+## License
+
+MIT
+
+## Disclaimer
+
+This project has nothing in common with the
+[getpaid](http://code.google.com/p/getpaid/) plone project.
+
+## Credits
+
+Created by [Dominik Kozaczko](https://github.com/dekoza).

python_getpaid_payu-0.1.0/README.md

@@ -0,0 +1,128 @@
+# getpaid-payu
+
+[![PyPI](https://img.shields.io/pypi/v/python-getpaid-payu.svg)](https://pypi.org/project/python-getpaid-payu/)
+[![Python Version](https://img.shields.io/pypi/pyversions/python-getpaid-payu)](https://pypi.org/project/python-getpaid-payu/)
+[![License](https://img.shields.io/pypi/l/python-getpaid-payu)](https://github.com/django-getpaid/python-getpaid-payu/blob/main/LICENSE)
+
+PayU payment gateway plugin for the
+[python-getpaid](https://github.com/django-getpaid) ecosystem. Provides a
+fully async HTTP client (`PayUClient`) and a payment processor
+(`PayUProcessor`) implementing the
+[getpaid-core](https://github.com/django-getpaid/python-getpaid-core)
+`BaseProcessor` interface. Communicates with PayU via their REST API v2.1
+using OAuth2 authentication.
+
+## Architecture
+
+getpaid-payu is composed of two main layers:
+
+- **PayUClient** — a low-level async HTTP client (built on `httpx`) that wraps
+  every PayU REST API v2.1 endpoint. OAuth2 tokens are obtained lazily and
+  refreshed automatically. Can be used as an async context manager for
+  connection reuse.
+- **PayUProcessor** — a high-level processor that implements `BaseProcessor`
+  from getpaid-core. Translates between the core payment protocol and PayU's
+  API, handles signature verification, PUSH/PULL callbacks, and FSM
+  transitions.
+
+## Key Features
+
+- Full PayU REST API v2.1 coverage
+- Async HTTP client with automatic OAuth2 token management
+- Create order, cancel, capture (charge), retrieve order info
+- Refund operations: create, retrieve single, retrieve all
+- Payment methods retrieval
+- Transaction details retrieval
+- Shop info and payout operations
+- Token deletion (card-on-file)
+- Automatic amount centification (amounts × 100) and normalization
+- Signature verification (MD5 and SHA-256)
+- PUSH callback handling with FSM integration
+- PULL status polling
+- Full pre-authorization support (lock, charge, release)
+
+## Quick Usage
+
+`PayUClient` can be used standalone as an async context manager:
+
+```python
+from decimal import Decimal
+from getpaid_payu.client import PayUClient
+from getpaid_payu.types import Currency
+
+async with PayUClient(
+    api_url="https://secure.snd.payu.com/",
+    pos_id=300746,
+    second_key="b6ca15b0d1020e8094f2b...",
+    oauth_id=300746,
+    oauth_secret="2ee86a66e5d97e3fadc4...",
+) as client:
+    response = await client.new_order(
+        amount=Decimal("29.99"),
+        currency=Currency.PLN,
+        order_id="order-123",
+        description="Test order",
+    )
+    redirect_url = response["redirectUri"]
+```
+
+## Configuration
+
+When used via a framework adapter (e.g. django-getpaid), configuration is
+provided as a dictionary:
+
+| Key | Type | Default | Description |
+|-----|------|---------|-------------|
+| `pos_id` | `int` | — | PayU POS (point of sale) identifier |
+| `second_key` | `str` | — | Second key (MD5) from PayU panel, used for signature verification |
+| `oauth_id` | `int` | — | OAuth client ID from PayU panel |
+| `oauth_secret` | `str` | — | OAuth client secret from PayU panel |
+| `sandbox` | `bool` | `True` | Use sandbox (`secure.snd.payu.com`) or production (`secure.payu.com`) |
+| `notify_url` | `str` | `None` | Notification callback URL template, e.g. `https://example.com/payments/{payment_id}/notify` |
+| `continue_url` | `str` | `None` | Redirect URL template after payment, e.g. `https://example.com/payments/{payment_id}/continue` |
+
+Example configuration dict:
+
+```python
+GETPAID_BACKENDS = {
+    "payu": {
+        "pos_id": 300746,
+        "second_key": "b6ca15b0d1020e8094f2b...",
+        "oauth_id": 300746,
+        "oauth_secret": "2ee86a66e5d97e3fadc4...",
+        "sandbox": True,
+        "notify_url": "https://example.com/payments/{payment_id}/notify",
+        "continue_url": "https://example.com/payments/{payment_id}/continue",
+    }
+}
+```
+
+## Supported Currencies
+
+BGN, CHF, CZK, DKK, EUR, GBP, HRK, HUF, NOK, PLN, RON, RUB, SEK, UAH, USD
+
+## Requirements
+
+- Python 3.12+
+- `python-getpaid-core >= 0.1.0`
+- `httpx >= 0.27.0`
+
+## Related Projects
+
+- [getpaid-core](https://github.com/django-getpaid/python-getpaid-core) —
+  framework-agnostic payment processing library
+- [django-getpaid](https://github.com/django-getpaid/django-getpaid) —
+  Django framework adapter
+
+## License
+
+MIT
+
+## Disclaimer
+
+This project has nothing in common with the
+[getpaid](http://code.google.com/p/getpaid/) plone project.
+
+## Credits
+
+Created by [Dominik Kozaczko](https://github.com/dekoza).

python_getpaid_payu-0.1.0/docs/changelog.md

@@ -0,0 +1,22 @@
+# Changelog
+
+## v0.1.0 (2026-02-14)
+
+Initial release.
+
+### Features
+
+- Full PayU REST API v2.1 coverage
+- Async HTTP client (`PayUClient`) with OAuth2 token management
+- Payment processor (`PayUProcessor`) implementing `BaseProcessor`
+- All order operations: create, cancel, capture, retrieve
+- Refund operations: create, retrieve single/all
+- Payment methods retrieval
+- Transaction details retrieval
+- Shop info and payout operations
+- Token deletion
+- Automatic amount centification/normalization
+- Signature verification (MD5 and SHA-256)
+- PUSH callback handling with FSM integration
+- PULL status polling
+- Full pre-authorization support (lock, charge, release)

python_getpaid_payu-0.1.0/docs/codeofconduct.md

@@ -0,0 +1,2 @@
+:::{include} ../CODE_OF_CONDUCT.md
+:::