Django-payments

Latest version: v2.0.0

Safety actively analyzes 619231 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

2.0.0

------

- **Breaking**: The `todopago` backend has been dropped. The payment provider
has [quite suddenly] announced it's shutting down.
- Older versions of ``django-phonenumber-field`` are now also supported. There
was no intrinsic incompatibility; the pinned version was merely too
restrictive.
- Various documentation improvements.

1.2.3

++++++++++++++++++
* better distinct PayU API errors

1.2.2

++++++++++++++++++
* solve the duplicate order case that errored already confirmed payment

1.2.1

++++++++++++++++++
* set fraud status if PayU anti-froud error
* store PayU error on payment

1.2.0

++++++++++++++++++
* user Payment.billing_* correctly - the functions like ``get_user`` or ``get_user_email``, ``get_user_first_name`` and ``get_user_last_name`` were redundant and are not called anymore.
* Shop name is taken from provider configuration variable ``shop_name``

1.1.0

++++++++++++++++++
* redirect to payment.get_failure_url() after API error, log the error

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.