django-payments-chile
django-payments-chile es una extensión para django-payments, una biblioteca que proporciona una interfaz universal para procesar pagos en aplicaciones Django. Este proyecto añade soporte específico para varios proveedores de pagos chilenos como Flow, Khipu, Webpay, y otros.
⚠️ ⚠️ Este proyecto está en desarrollo activo, usar con precaución. ⚠️ ⚠️
Proveedores de pago soportados
| Proveedor | Estado | Descripcion |
|---|---|---|
| Flow | ✅ | Plataforma chilena para pagos en línea que admite múltiples métodos de pago. |
| Khipu | ✅ | Permite pagos mediante transferencia electrónica en tiempo real. |
| Klap | ❌ | Solución de pagos electrónicos enfocados en comercios. |
| Kushki | ❌ | Proveedor de pagos electrónicos que facilita la integración con diversas plataformas. |
| Payku | ❌ | Plataforma de pagos enfocada en pequeñas y medianas empresas. |
| Webpay | ✅ | El sistema de pago en línea más utilizado en Chile, operado por Transbank. |
Características
- Soporte para múltiples proveedores de pago en un solo proyecto.
- API consistente para crear, procesar y verificar transacciones.
- Fácil configuración y personalización.
- Documentación clara para desarrolladores.
- Soporte para eventos de éxito, fallo, y reembolsos de pagos.
Instalación
La biblioteca django-payments-chile está disponible en PyPi. Puedes instalarla fácilmente con tu gestor de paquetes favorito, como pip, poetry, o pipenv.
pip install django-payments-chile
Configuración de Proveedores
Agrega las credenciales de los proveedores de pago en tu archivo de configuración:
PAYMENT_VARIANTS = {
'flow': ('django_payments_chile.FlowProvider', {
'api_key': 'tu_api_key_flow',
'secret': 'tu_secret_flow',
}),
'webpay': ('django_payments_chile.WebpayProvider', {
'commerce_code': 'tu_commerce_code_webpay',
'api_key': 'tu_api_key_webpay',
}),
}
Licencia
Este proyecto no está afiliado, asociado ni patrocinado por ninguna de las empresas mencionadas en el listado de compatibilidad.
El código de este proyecto está disponible bajo la licencia MIT, lo que significa que puedes utilizarlo, modificarlo y distribuirlo de manera libre, sujeto a las condiciones establecidas en dicha licencia.
1 maintainer
Metadata
1 maintainer
Release files for django-payments-chile 2024.12.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django_payments_chile-2024.12.5.tar.gz | 10.3 kB | With provenance | Details for django_payments_chile-2024.12.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_payments_chile-2024.12.5-py3-none-any.whl | Python 3 | none | any | Details for django_payments_chile-2024.12.5-py3-none-any.whl |
Total release size: 23.3 kB
Release files / django_payments_chile-2024.12.5.tar.gz
| Download URL | django_payments_chile-2024.12.5.tar.gz |
|---|---|
| Size | 10.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5503b06cf6bd392cfe34f44503fabdf9cd9dea379dec56411a047e512c6c0a98
|
|
BLAKE2b-256 checksum How to use checksums |
feeabc6d0f087b06afe1ff963001b2ad9c7a1675b76e568f525e334ad54dcbb4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 19, 2024.
Transparency logRelease files / django_payments_chile-2024.12.5-py3-none-any.whl
| Download URL | django_payments_chile-2024.12.5-py3-none-any.whl |
|---|---|
| Size | 13.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
758813d16b3ba1471b9ecd7eb8d748c547c36c5e80db2014b3eb2728dcb0566a
|
|
BLAKE2b-256 checksum How to use checksums |
249a255f0a3adbf38fa2fa36b5d4909410352135aeecd8031cde6112330d1362
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 19, 2024.
Transparency logSecurity for django-payments-chile 2024.12.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for django_payments_chile-2024.12.5.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 19, 2024.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
