Django-payments

Latest version: v3.0.1

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

Scan your dependencies

Page 1 of 5

3.0.1

------

This version is functionally identically to v3.0.0, and only includes a fix in
our pipeline that prevented the previous version from being published to PyPI.

3.0.0

------
- **BREAKING**: Dropped support for Django 2.2, 3.0, 3.1 and 4.0.
Supported versions of Django are 3.2 (LTS), 4.1 and 4.2.
- Stripe backends now sends order_id in the metadata parameter.
- A new ``StripeProviderV3`` has been added using the latest Stripe API.
- Added support for Python 3.11, Django 4.1 and Django 4.2.
- Stripe backends now supports webhooks
- New :ref:`webhook settings <webhooks>`
- Fixed PayPal backends not saving captured_amount when processing data.
- Fixed ``base_payment.refund()`` not making any refund
- PayPal backends now perform a full refund if ``amount=None``.
- Added support for Django 5.0.
- Added support for Django 5.1.

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.5.0

******************
* log warning when status changes out from confirmed
* fix problem with form in Django 5.0
* support Django 5.1

1.4.6

******************
* remove debug code committed by mistake

1.4.5

******************
* fix safestring in Django 5.0

Page 1 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.