python-redsys 1.2.2__tar.gz → 2.0.0__tar.gz

python_redsys-2.0.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        https://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 [yyyy] [name of copyright owner]
+
+   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
+
+       https://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.

python_redsys-2.0.0/NOTICE

@@ -0,0 +1,7 @@
+python-redsys
+Copyright 2016-2026 David Díaz
+
+Licensed under the Apache License, Version 2.0 (the "License").
+You may obtain a copy of the License at:
+
+    https://www.apache.org/licenses/LICENSE-2.0

python_redsys-2.0.0/PKG-INFO

@@ -0,0 +1,214 @@
+Metadata-Version: 2.4
+Name: python-redsys
+Version: 2.0.0
+Summary: A simple, lightweight client to handle payments through the RedSys platform.
+Author-email: David Díaz <d.diazp@gmail.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/ddiazpinto/python-redsys
+Project-URL: Source, https://github.com/ddiazpinto/python-redsys
+Keywords: redsys,sermepa,tpv,payments,psd2
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3.15
+Classifier: Topic :: Office/Business :: Financial
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: cryptography>=49
+Requires-Dist: pydantic>=2.13
+Provides-Extra: http
+Requires-Dist: httpx>=0.26; extra == "http"
+Dynamic: license-file
+
+# Welcome to python-redsys!
+
+[![CI](https://github.com/ddiazpinto/python-redsys/actions/workflows/ci.yml/badge.svg)](https://github.com/ddiazpinto/python-redsys/actions/workflows/ci.yml) [![Coverage](https://codecov.io/gh/ddiazpinto/python-redsys/branch/master/graph/badge.svg)](https://codecov.io/gh/ddiazpinto/python-redsys) [![PyPI](https://img.shields.io/pypi/v/python-redsys.svg)](https://pypi.org/project/python-redsys/) ![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg) [![License: Apache 2.0](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](https://www.apache.org/licenses/LICENSE-2.0)
+
+A simple, lightweight client to handle payments through the RedSys platform, covering both connection types it defines: *redirect connection* (browser form POST) and *direct connection* (server-to-server REST).
+
+The library builds the signed request and verifies and parses the response. The redirect form is submitted by the cardholder's browser; the direct REST call is made by the integrator's HTTP client or by the optional `http` extra (`httpx`).
+
+For Django, see [django-redsys](https://github.com/ddiazpinto/django-redsys).
+
+## Installation
+
+```bash
+pip install python-redsys
+
+# optional: the direct-connection sender (httpx)
+pip install "python-redsys[http]"
+```
+
+Requires Python 3.10+. Runtime dependencies: `cryptography` and `pydantic` (v2).
+
+## Upgrading from 1.x
+
+2.0 has a new API. The [migration guide](docs/migration-1x-to-2x.md) lists every change; 1.x receives fixes until 2026-12-31.
+
+## Usage
+
+The client is the single entry point: an operation method (`payment`, `preauthorization`, `confirmation`, `refund`, `cancellation`) returns a `Request`, with `.to_dict()` for the redirect POST fields and `.send()` for the direct REST call. Fields are validated on construction; `amount` is a `Decimal`. A parameter the library does not model yet is passed by its wire name (`Ds_Merchant_...`), sent as given, with an `UnknownParameterWarning`.
+
+## Using *redirect connection*
+
+### 1. Build a signed request
+
+```python
+from decimal import Decimal, ROUND_HALF_UP
+from redsys import currencies
+from redsys.clients import RedirectClient
+
+client = RedirectClient(
+    secret_key="123456789abcdef",
+    merchant_code="100000001",
+    terminal=1,
+    sandbox=False,
+)
+
+post_parameters = client.payment(
+    order="000000001",
+    currency=currencies.EUR,
+    # The amount is a Decimal; pre-quantize to two decimals.
+    amount=Decimal("10.56489").quantize(Decimal(".01"), ROUND_HALF_UP),
+    merchant_url="https://example.com/redsys/response",
+    url_ok="https://example.com/ok",
+    url_ko="https://example.com/ko",
+    merchant_name="Example Commerce",
+    product_description="Products of Example Commerce",
+).to_dict()  # Ds_SignatureVersion / Ds_MerchantParameters / Ds_Signature
+```
+
+Bizum: add `pay_methods="z"` (and optionally `bizum_mobile_number`) to the payment.
+
+### 2. Communication step
+
+Auto-submit an HTML form (`method="POST"`) to `client.endpoint` with the three `post_parameters` fields. RedSys notifies the result both as a server-to-server POST to `merchant_url` and as a browser redirect to `url_ok` / `url_ko`.
+
+### 3. Verify and read the response
+
+`parse_response()` accepts the received parameters (callback form fields or REST JSON body) and raises `ValueError` on signature mismatch.
+
+```python
+response = client.parse_response(received)  # received: the Ds_* dict RedSys posted back
+
+if response.is_paid():
+    ...  # actions after a successful payment
+else:
+    raise Exception(f"declined with code {response.response_code}")
+```
+
+Response predicates (per the RedSys documentation):
+
+- `response.is_paid()`: response code between 0 and 99.
+- `response.is_canceled()`: response code 400.
+- `response.is_refunded()`: response code 900.
+- `response.is_authorized()`: paid, refunded or canceled.
+
+`response.response_code` is the raw RedSys code; meanings are listed in [`docs/response-codes.md`](docs/response-codes.md). Decoded fields (`response.order`, `response.amount` as a `Decimal`, ...) read off the model; parameters the library does not list are kept under their wire name in `response.model_extra`.
+
+## Using *direct connection* (REST)
+
+The direct connection exchanges the same signed envelope server-to-server as JSON. Build the operation with the same methods: `.send()` performs the call, `.to_dict()` returns the JSON body for your own HTTP client.
+
+With the optional sender (`pip install "python-redsys[http]"`):
+
+```python
+from decimal import Decimal
+from redsys import currencies
+from redsys.clients import DirectClient
+
+client = DirectClient(secret_key="123456789abcdef", merchant_code="100000001",
+                      terminal=1, sandbox=True)
+
+response = client.refund(
+    order="000000001", amount=Decimal("10.56"), currency=currencies.EUR,
+).send()  # signs, POSTs, verifies, parses
+response.is_refunded()
+```
+
+Asynchronous (`httpx.AsyncClient`), with `send()` awaitable:
+
+```python
+from redsys.clients import AsyncDirectClient
+
+client = AsyncDirectClient(secret_key="123456789abcdef", merchant_code="100000001",
+                           terminal=1, sandbox=True)
+response = await client.payment(
+    order="000000001", amount=Decimal("10.56"), currency=currencies.EUR,
+    pan="...", expiry_date="2512", cvv2="...",
+).send()
+```
+
+Transport-agnostic (do your own HTTP):
+
+```python
+body = client.refund(order="000000001", amount=Decimal("10.56"),
+                     currency=currencies.EUR).to_dict()  # JSON body to POST
+# ... POST body to client.endpoint with your HTTP client ...
+response = client.parse_response(received_json)  # verifies and parses
+```
+
+`parse_response()` raises `redsys.exceptions.ResponseError` when RedSys answers with an error code instead of a signed result.
+
+## inSite (hosted fields)
+
+inSite captures the card in the browser via RedSys's JavaScript and yields an `idoper` token, keeping the PAN off your server. The card-capture JS is the front-end's responsibility; the backend completes the operation as a direct payment carrying the token:
+
+```python
+client.payment(order="000000001", amount=Decimal("10.56"), currency=currencies.EUR,
+               idoper="<token from the inSite JS>").send()
+```
+
+## Tokenization and recurring (COF / MIT)
+
+Store a card on the first payment and charge it later without card data. The first payment requests a token and flags the credential-on-file intent; RedSys returns a token and a COF transaction id that subsequent merchant-initiated charges reuse.
+
+```python
+from decimal import Decimal
+from redsys import cof, currencies, sca
+from redsys.clients import DirectClient
+
+client = DirectClient(secret_key="123456789abcdef", merchant_code="100000001",
+                      terminal=1, sandbox=True)
+
+# 1. First payment, request a token (cardholder present)
+response = client.payment(
+    order="000000001", amount=Decimal("10.56"), currency=currencies.EUR,
+    pan="...", expiry_date="YYMM", cvv2="...",
+    identifier=cof.REQUEST_TOKEN, cof_ini=cof.INITIAL, cof_type=cof.RECURRING,
+).send()
+token, cof_txnid = response.identifier, response.cof_txnid
+
+# 2. Later merchant-initiated charge, no card data
+client.payment(
+    order="000000002", amount=Decimal("10.56"), currency=currencies.EUR,
+    identifier=token, cof_ini=cof.SUBSEQUENT, cof_type=cof.RECURRING, cof_txnid=cof_txnid,
+    excep_sca=sca.MIT, direct_payment="true",
+).send()
+```
+
+`redsys.cof` provides the indicator constants (`INITIAL`/`SUBSEQUENT`, `RECURRING`/`INSTALLMENT`/...) and the `REQUEST_TOKEN` sentinel. The periodic fields (`sum_total`, `date_frequency`, `charge_expiry_date`) are also accepted by `DirectClient.payment()`. `redsys.sca` holds the PSD2 exemption codes for `excep_sca` (`LWV`, `TRA`, `MIT`, `COR`, `ATD`); `sca.QUERY` on `inicia()` asks which exemptions the card allows, returned in `response.excep_sca`.
+
+## Signature versions
+
+`signature_version` on the client constructor selects the scheme; the constants are in `redsys.clients`.
+
+- `HMAC_SHA512_V2` (AES-128 + HMAC-SHA512): the default, as in RedSys's redirection guide and libraries.
+- `HMAC_SHA512_V1`: the same algorithm with padded encoding, as in the REST guide.
+- `HMAC_SHA256_V1` (3DES): legacy, still accepted by RedSys.
+
+## Reference
+
+- [`docs/response-codes.md`](docs/response-codes.md): response-code meanings.
+- [`docs/redirect-connection.md`](docs/redirect-connection.md) / [`docs/direct-connection.md`](docs/direct-connection.md): connection-type protocol reference.
+
+## Contributing
+
+Dev setup, checks and live tests are in [`CONTRIBUTING.md`](CONTRIBUTING.md); contributors are listed in [`CONTRIBUTORS.md`](CONTRIBUTORS.md).

python_redsys-2.0.0/README.md

@@ -0,0 +1,185 @@
+# Welcome to python-redsys!
+
+[![CI](https://github.com/ddiazpinto/python-redsys/actions/workflows/ci.yml/badge.svg)](https://github.com/ddiazpinto/python-redsys/actions/workflows/ci.yml) [![Coverage](https://codecov.io/gh/ddiazpinto/python-redsys/branch/master/graph/badge.svg)](https://codecov.io/gh/ddiazpinto/python-redsys) [![PyPI](https://img.shields.io/pypi/v/python-redsys.svg)](https://pypi.org/project/python-redsys/) ![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg) [![License: Apache 2.0](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](https://www.apache.org/licenses/LICENSE-2.0)
+
+A simple, lightweight client to handle payments through the RedSys platform, covering both connection types it defines: *redirect connection* (browser form POST) and *direct connection* (server-to-server REST).
+
+The library builds the signed request and verifies and parses the response. The redirect form is submitted by the cardholder's browser; the direct REST call is made by the integrator's HTTP client or by the optional `http` extra (`httpx`).
+
+For Django, see [django-redsys](https://github.com/ddiazpinto/django-redsys).
+
+## Installation
+
+```bash
+pip install python-redsys
+
+# optional: the direct-connection sender (httpx)
+pip install "python-redsys[http]"
+```
+
+Requires Python 3.10+. Runtime dependencies: `cryptography` and `pydantic` (v2).
+
+## Upgrading from 1.x
+
+2.0 has a new API. The [migration guide](docs/migration-1x-to-2x.md) lists every change; 1.x receives fixes until 2026-12-31.
+
+## Usage
+
+The client is the single entry point: an operation method (`payment`, `preauthorization`, `confirmation`, `refund`, `cancellation`) returns a `Request`, with `.to_dict()` for the redirect POST fields and `.send()` for the direct REST call. Fields are validated on construction; `amount` is a `Decimal`. A parameter the library does not model yet is passed by its wire name (`Ds_Merchant_...`), sent as given, with an `UnknownParameterWarning`.
+
+## Using *redirect connection*
+
+### 1. Build a signed request
+
+```python
+from decimal import Decimal, ROUND_HALF_UP
+from redsys import currencies
+from redsys.clients import RedirectClient
+
+client = RedirectClient(
+    secret_key="123456789abcdef",
+    merchant_code="100000001",
+    terminal=1,
+    sandbox=False,
+)
+
+post_parameters = client.payment(
+    order="000000001",
+    currency=currencies.EUR,
+    # The amount is a Decimal; pre-quantize to two decimals.
+    amount=Decimal("10.56489").quantize(Decimal(".01"), ROUND_HALF_UP),
+    merchant_url="https://example.com/redsys/response",
+    url_ok="https://example.com/ok",
+    url_ko="https://example.com/ko",
+    merchant_name="Example Commerce",
+    product_description="Products of Example Commerce",
+).to_dict()  # Ds_SignatureVersion / Ds_MerchantParameters / Ds_Signature
+```
+
+Bizum: add `pay_methods="z"` (and optionally `bizum_mobile_number`) to the payment.
+
+### 2. Communication step
+
+Auto-submit an HTML form (`method="POST"`) to `client.endpoint` with the three `post_parameters` fields. RedSys notifies the result both as a server-to-server POST to `merchant_url` and as a browser redirect to `url_ok` / `url_ko`.
+
+### 3. Verify and read the response
+
+`parse_response()` accepts the received parameters (callback form fields or REST JSON body) and raises `ValueError` on signature mismatch.
+
+```python
+response = client.parse_response(received)  # received: the Ds_* dict RedSys posted back
+
+if response.is_paid():
+    ...  # actions after a successful payment
+else:
+    raise Exception(f"declined with code {response.response_code}")
+```
+
+Response predicates (per the RedSys documentation):
+
+- `response.is_paid()`: response code between 0 and 99.
+- `response.is_canceled()`: response code 400.
+- `response.is_refunded()`: response code 900.
+- `response.is_authorized()`: paid, refunded or canceled.
+
+`response.response_code` is the raw RedSys code; meanings are listed in [`docs/response-codes.md`](docs/response-codes.md). Decoded fields (`response.order`, `response.amount` as a `Decimal`, ...) read off the model; parameters the library does not list are kept under their wire name in `response.model_extra`.
+
+## Using *direct connection* (REST)
+
+The direct connection exchanges the same signed envelope server-to-server as JSON. Build the operation with the same methods: `.send()` performs the call, `.to_dict()` returns the JSON body for your own HTTP client.
+
+With the optional sender (`pip install "python-redsys[http]"`):
+
+```python
+from decimal import Decimal
+from redsys import currencies
+from redsys.clients import DirectClient
+
+client = DirectClient(secret_key="123456789abcdef", merchant_code="100000001",
+                      terminal=1, sandbox=True)
+
+response = client.refund(
+    order="000000001", amount=Decimal("10.56"), currency=currencies.EUR,
+).send()  # signs, POSTs, verifies, parses
+response.is_refunded()
+```
+
+Asynchronous (`httpx.AsyncClient`), with `send()` awaitable:
+
+```python
+from redsys.clients import AsyncDirectClient
+
+client = AsyncDirectClient(secret_key="123456789abcdef", merchant_code="100000001",
+                           terminal=1, sandbox=True)
+response = await client.payment(
+    order="000000001", amount=Decimal("10.56"), currency=currencies.EUR,
+    pan="...", expiry_date="2512", cvv2="...",
+).send()
+```
+
+Transport-agnostic (do your own HTTP):
+
+```python
+body = client.refund(order="000000001", amount=Decimal("10.56"),
+                     currency=currencies.EUR).to_dict()  # JSON body to POST
+# ... POST body to client.endpoint with your HTTP client ...
+response = client.parse_response(received_json)  # verifies and parses
+```
+
+`parse_response()` raises `redsys.exceptions.ResponseError` when RedSys answers with an error code instead of a signed result.
+
+## inSite (hosted fields)
+
+inSite captures the card in the browser via RedSys's JavaScript and yields an `idoper` token, keeping the PAN off your server. The card-capture JS is the front-end's responsibility; the backend completes the operation as a direct payment carrying the token:
+
+```python
+client.payment(order="000000001", amount=Decimal("10.56"), currency=currencies.EUR,
+               idoper="<token from the inSite JS>").send()
+```
+
+## Tokenization and recurring (COF / MIT)
+
+Store a card on the first payment and charge it later without card data. The first payment requests a token and flags the credential-on-file intent; RedSys returns a token and a COF transaction id that subsequent merchant-initiated charges reuse.
+
+```python
+from decimal import Decimal
+from redsys import cof, currencies, sca
+from redsys.clients import DirectClient
+
+client = DirectClient(secret_key="123456789abcdef", merchant_code="100000001",
+                      terminal=1, sandbox=True)
+
+# 1. First payment, request a token (cardholder present)
+response = client.payment(
+    order="000000001", amount=Decimal("10.56"), currency=currencies.EUR,
+    pan="...", expiry_date="YYMM", cvv2="...",
+    identifier=cof.REQUEST_TOKEN, cof_ini=cof.INITIAL, cof_type=cof.RECURRING,
+).send()
+token, cof_txnid = response.identifier, response.cof_txnid
+
+# 2. Later merchant-initiated charge, no card data
+client.payment(
+    order="000000002", amount=Decimal("10.56"), currency=currencies.EUR,
+    identifier=token, cof_ini=cof.SUBSEQUENT, cof_type=cof.RECURRING, cof_txnid=cof_txnid,
+    excep_sca=sca.MIT, direct_payment="true",
+).send()
+```
+
+`redsys.cof` provides the indicator constants (`INITIAL`/`SUBSEQUENT`, `RECURRING`/`INSTALLMENT`/...) and the `REQUEST_TOKEN` sentinel. The periodic fields (`sum_total`, `date_frequency`, `charge_expiry_date`) are also accepted by `DirectClient.payment()`. `redsys.sca` holds the PSD2 exemption codes for `excep_sca` (`LWV`, `TRA`, `MIT`, `COR`, `ATD`); `sca.QUERY` on `inicia()` asks which exemptions the card allows, returned in `response.excep_sca`.
+
+## Signature versions
+
+`signature_version` on the client constructor selects the scheme; the constants are in `redsys.clients`.
+
+- `HMAC_SHA512_V2` (AES-128 + HMAC-SHA512): the default, as in RedSys's redirection guide and libraries.
+- `HMAC_SHA512_V1`: the same algorithm with padded encoding, as in the REST guide.
+- `HMAC_SHA256_V1` (3DES): legacy, still accepted by RedSys.
+
+## Reference
+
+- [`docs/response-codes.md`](docs/response-codes.md): response-code meanings.
+- [`docs/redirect-connection.md`](docs/redirect-connection.md) / [`docs/direct-connection.md`](docs/direct-connection.md): connection-type protocol reference.
+
+## Contributing
+
+Dev setup, checks and live tests are in [`CONTRIBUTING.md`](CONTRIBUTING.md); contributors are listed in [`CONTRIBUTORS.md`](CONTRIBUTORS.md).

python_redsys-2.0.0/pyproject.toml

@@ -0,0 +1,66 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "python-redsys"
+version = "2.0.0"
+description = "A simple, lightweight client to handle payments through the RedSys platform."
+readme = "README.md"
+requires-python = ">=3.10"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+authors = [{ name = "David Díaz", email = "d.diazp@gmail.com" }]
+keywords = ["redsys", "sermepa", "tpv", "payments", "psd2"]
+dependencies = ["cryptography>=49", "pydantic>=2.13"]
+classifiers = [
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Programming Language :: Python :: 3.15",
+    "Topic :: Office/Business :: Financial",
+]
+
+[project.urls]
+Homepage = "https://github.com/ddiazpinto/python-redsys"
+Source = "https://github.com/ddiazpinto/python-redsys"
+
+[project.optional-dependencies]
+# 0.26 is the oldest httpx that imports on Python 3.13 and later.
+http = ["httpx>=0.26"]
+
+[dependency-groups]
+test = ["pytest>=8.4", "pytest-cov"]
+lint = ["ruff", "mypy"]
+dev = [
+    { include-group = "test" },
+    { include-group = "lint" },
+    "pre-commit",
+]
+
+[tool.setuptools.packages.find]
+include = ["redsys*"]
+exclude = ["tests*"]
+
+[tool.setuptools.package-data]
+redsys = ["py.typed"]
+
+[tool.ruff]
+line-length = 120
+target-version = "py310"
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "B", "UP"]
+
+[tool.ruff.format]
+quote-style = "single"
+
+[tool.mypy]
+python_version = "3.10"
+ignore_missing_imports = true
+exclude = ["build/"]