deepayment 0.1.0__tar.gz

deepayment-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://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 2026 DEEPayment
+
+   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
+
+       http://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.

deepayment-0.1.0/PKG-INFO

@@ -0,0 +1,170 @@
+Metadata-Version: 2.4
+Name: deepayment
+Version: 0.1.0
+Summary: Merchant open API SDK (Ed25519 / RFC 9421 signing, X25519 sealed box body encryption)
+Author-email: DEEPayment <support@deepayment.com>
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/deepayment/sdk-python
+Project-URL: Repository, https://github.com/deepayment/sdk-python
+Project-URL: Issues, https://github.com/deepayment/sdk-python/issues
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Office/Business :: Financial
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pynacl>=1.5
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == "dev"
+Dynamic: license-file
+
+# DEEPayment SDK for Python
+
+Python SDK for the merchant open API. Signing, digesting and body encryption are
+handled by the SDK; merchants never assemble `Signature-Input`, `Content-Digest`
+or the sealed box envelope themselves.
+
+## Protocol
+
+[`protocol/`](protocol/) is the source of truth, shared with the Go / JavaScript /
+PHP / Java SDKs through one set of test vectors:
+
+| Item | Approach |
+| --- | --- |
+| Signature | Ed25519 + fixed RFC 9421 profile |
+| Digest | RFC 9530 `Content-Digest` (sha-256) |
+| POST body | X25519 sealed box envelope; the digest covers the sealed body |
+| GET | No encryption, no body; only the public query and access key are signed |
+| Webhook | Platform Ed25519 signature, plaintext body |
+| Merchant identity | Located by `Merchant-Access-Key` only; signature params carry **no keyId** |
+
+## Installation
+
+```
+pip install deepayment
+```
+
+Runtime dependency: pynacl. Python 3.10 or newer.
+
+## Configuration
+
+Six values; only the private key is generated on the merchant side, and the
+platform never receives it:
+
+| Field | Meaning |
+| --- | --- |
+| `base_url` | HTTPS platform origin, without `/api/v1` |
+| `access_key` | Merchant access key issued by the platform |
+| `merchant_private_key_base64` | Merchant Ed25519 private key, **kept on the merchant side only** |
+| `platform_body_key_id` | Current platform body key id (per deployment) |
+| `platform_body_public_key_base64` | Platform X25519 public key used to seal POST bodies |
+| `platform_webhook_public_keys` | Platform webhook Ed25519 public keys, indexed by keyId |
+
+`Client` rejects non-HTTPS base URLs. Synchronous responses remain plaintext JSON
+and rely on HTTPS/TLS for confidentiality and integrity.
+
+## Quick start
+
+```python
+from deepayment import APIError, Client, CreatePaymentReq, RequestError, ResponseError, TransportError
+
+client = Client(
+    base_url="https://panama.deepayment.com",          # production origin; no /api/v1
+    access_key="mak_live_xxx",
+    merchant_private_key_base64=merchant_private_key,          # merchant Ed25519 private key, base64
+    platform_body_key_id="body_20260827_01",
+    platform_body_public_key_base64=platform_body_public_key,  # platform X25519 public key, base64
+    platform_webhook_public_keys={                             # keyId -> platform Ed25519 public key, base64
+        "pwhk_20260827_01": platform_webhook_public_key,
+    },
+)
+
+order = client.create_payment(CreatePaymentReq(
+    merchantOrderNo="M20260101001",
+    currency="BRL",
+    amount="100.00",                                   # decimal string, never a float
+    paymentMethod={"code": "PIX", "pix": {"payerName": "Joao Silva"}},
+    webhookUrl="https://merchant.example/webhook/payments",
+))
+print(order.orderNo, order.status, order.action.url)
+```
+
+### Two kinds of failure, opposite handling
+
+| Error | Meaning | Handling |
+| --- | --- | --- |
+| `RequestError` | Rejected **before it was sent** (local validation, a bad parameter, or a request the SDK could not encode or sign) | Safe to mark failed; fix the request and retry under the same `merchantOrderNo` |
+| `TransportError` | Handed to the transport, no usable response (connection failure, timeout, interrupted read) | Outcome unknown; **never mark a payout failed**. Query by `merchantOrderNo`, or resend the identical request under the same number |
+| `APIError` | The gateway returned a business error (`msg` / `message` / `trace_id`) | Branch on `msg`. `IDEMPOTENCY_CONFLICT`: the number is already in flight, query it and keep querying rather than switching numbers. `CHANNEL_ERROR`: the order may already exist, query by `merchantOrderNo` first |
+| `ResponseError` | The gateway or CDN returned something that is not an envelope (HTML 502, ...) | Outcome unknown; query before deciding |
+| `ResponseTooLargeError` | A response arrived but exceeded the size limit and was discarded | Outcome unknown; the order was most likely created, query before deciding |
+| Anything else | An unexpected error; assume the request may have arrived | Outcome unknown; query before deciding |
+
+**`merchantOrderNo` is the only key that prevents a duplicate order.** A second
+create with the same number never creates a second order: the platform answers
+with the original order, or with `IDEMPOTENCY_CONFLICT` while the first one is
+still being placed. The idempotency key travels with the request for tracing and
+is **not** a deduplication key.
+
+Two rules follow:
+
+- After an unknown outcome, never allocate a new `merchantOrderNo`. Query the
+  existing one, or resend the same request under the same number.
+- A resend must carry identical parameters. The platform returns the original
+  order without comparing fields, so a changed amount or account silently has no
+  effect. To change anything, use a new `merchantOrderNo` and reconcile the
+  original order first.
+
+The SDK validates locally before signing (top-level required fields and formats,
+method shape and required extras); the rules are defined in
+[`protocol/merchant-api.md`](protocol/merchant-api.md#client-side-validation).
+Format checks (phone length, e-mail, ...) stay with the gateway on purpose so the
+SDK cannot drift from it.
+
+### Next steps
+
+Queries, idempotent retries and webhook verification are covered by the platform
+documentation at <https://docs.deepayment.com>; its examples map one to one onto this
+SDK. The wire protocol is in
+[`protocol/webhook.md`](protocol/webhook.md) and
+[`protocol/merchant-api.md`](protocol/merchant-api.md). Key points:
+
+- After a create timeout, query by `merchantOrderNo` first instead of sending a
+  new order; a deliberate retry repeats the same call with the same `merchantOrderNo`.
+- For webhooks, pass the method, path, headers and the **raw, unparsed body bytes**
+  to `client.parse_payment_webhook(method=, path=, headers=, body=)`; the SDK checks
+  the digest, event id, time window and Ed25519 signature. Return 2xx once processed
+  and deduplicate by `eventId`.
+
+## Amounts
+
+Amounts, fees and rates in requests, responses, webhooks, balances, rates and
+receipts are **always decimal strings** such as `"100.00"`. Never use floats.
+
+## Order status
+
+There are exactly six external statuses: `PENDING` `PROCESSING` `SUCCEEDED`
+`FAILED` `EXPIRED` `CANCELED`.
+
+## Troubleshooting
+
+| Situation | Action |
+| --- | --- |
+| Create request timed out | Query by `merchantOrderNo`; do not send a new order |
+| Deliberate retry | Call the same method again with the same `merchantOrderNo` and identical parameters; the SDK regenerates the nonce on every request |
+| Signature rejected | Check the server clock, the access key, and that the merchant private key matches the public key registered with the platform |
+| Body decryption failed | Check that `platform_body_key_id` and the public key belong to the current environment |
+| Webhook signature rejected | Check that the webhook key set contains the `keyid` from the header |
+
+## Tests
+
+```
+python -m pip install -e '.[dev]'
+python -m pytest -q
+```
+
+The tests assert directly against the [`protocol/testdata`](protocol/testdata/)
+vectors: `Signature-Input`, the signature base and the signature value are compared
+byte for byte, and body encryption is verified by opening ciphertext produced by
+the reference implementation.

deepayment-0.1.0/README.md

@@ -0,0 +1,149 @@
+# DEEPayment SDK for Python
+
+Python SDK for the merchant open API. Signing, digesting and body encryption are
+handled by the SDK; merchants never assemble `Signature-Input`, `Content-Digest`
+or the sealed box envelope themselves.
+
+## Protocol
+
+[`protocol/`](protocol/) is the source of truth, shared with the Go / JavaScript /
+PHP / Java SDKs through one set of test vectors:
+
+| Item | Approach |
+| --- | --- |
+| Signature | Ed25519 + fixed RFC 9421 profile |
+| Digest | RFC 9530 `Content-Digest` (sha-256) |
+| POST body | X25519 sealed box envelope; the digest covers the sealed body |
+| GET | No encryption, no body; only the public query and access key are signed |
+| Webhook | Platform Ed25519 signature, plaintext body |
+| Merchant identity | Located by `Merchant-Access-Key` only; signature params carry **no keyId** |
+
+## Installation
+
+```
+pip install deepayment
+```
+
+Runtime dependency: pynacl. Python 3.10 or newer.
+
+## Configuration
+
+Six values; only the private key is generated on the merchant side, and the
+platform never receives it:
+
+| Field | Meaning |
+| --- | --- |
+| `base_url` | HTTPS platform origin, without `/api/v1` |
+| `access_key` | Merchant access key issued by the platform |
+| `merchant_private_key_base64` | Merchant Ed25519 private key, **kept on the merchant side only** |
+| `platform_body_key_id` | Current platform body key id (per deployment) |
+| `platform_body_public_key_base64` | Platform X25519 public key used to seal POST bodies |
+| `platform_webhook_public_keys` | Platform webhook Ed25519 public keys, indexed by keyId |
+
+`Client` rejects non-HTTPS base URLs. Synchronous responses remain plaintext JSON
+and rely on HTTPS/TLS for confidentiality and integrity.
+
+## Quick start
+
+```python
+from deepayment import APIError, Client, CreatePaymentReq, RequestError, ResponseError, TransportError
+
+client = Client(
+    base_url="https://panama.deepayment.com",          # production origin; no /api/v1
+    access_key="mak_live_xxx",
+    merchant_private_key_base64=merchant_private_key,          # merchant Ed25519 private key, base64
+    platform_body_key_id="body_20260827_01",
+    platform_body_public_key_base64=platform_body_public_key,  # platform X25519 public key, base64
+    platform_webhook_public_keys={                             # keyId -> platform Ed25519 public key, base64
+        "pwhk_20260827_01": platform_webhook_public_key,
+    },
+)
+
+order = client.create_payment(CreatePaymentReq(
+    merchantOrderNo="M20260101001",
+    currency="BRL",
+    amount="100.00",                                   # decimal string, never a float
+    paymentMethod={"code": "PIX", "pix": {"payerName": "Joao Silva"}},
+    webhookUrl="https://merchant.example/webhook/payments",
+))
+print(order.orderNo, order.status, order.action.url)
+```
+
+### Two kinds of failure, opposite handling
+
+| Error | Meaning | Handling |
+| --- | --- | --- |
+| `RequestError` | Rejected **before it was sent** (local validation, a bad parameter, or a request the SDK could not encode or sign) | Safe to mark failed; fix the request and retry under the same `merchantOrderNo` |
+| `TransportError` | Handed to the transport, no usable response (connection failure, timeout, interrupted read) | Outcome unknown; **never mark a payout failed**. Query by `merchantOrderNo`, or resend the identical request under the same number |
+| `APIError` | The gateway returned a business error (`msg` / `message` / `trace_id`) | Branch on `msg`. `IDEMPOTENCY_CONFLICT`: the number is already in flight, query it and keep querying rather than switching numbers. `CHANNEL_ERROR`: the order may already exist, query by `merchantOrderNo` first |
+| `ResponseError` | The gateway or CDN returned something that is not an envelope (HTML 502, ...) | Outcome unknown; query before deciding |
+| `ResponseTooLargeError` | A response arrived but exceeded the size limit and was discarded | Outcome unknown; the order was most likely created, query before deciding |
+| Anything else | An unexpected error; assume the request may have arrived | Outcome unknown; query before deciding |
+
+**`merchantOrderNo` is the only key that prevents a duplicate order.** A second
+create with the same number never creates a second order: the platform answers
+with the original order, or with `IDEMPOTENCY_CONFLICT` while the first one is
+still being placed. The idempotency key travels with the request for tracing and
+is **not** a deduplication key.
+
+Two rules follow:
+
+- After an unknown outcome, never allocate a new `merchantOrderNo`. Query the
+  existing one, or resend the same request under the same number.
+- A resend must carry identical parameters. The platform returns the original
+  order without comparing fields, so a changed amount or account silently has no
+  effect. To change anything, use a new `merchantOrderNo` and reconcile the
+  original order first.
+
+The SDK validates locally before signing (top-level required fields and formats,
+method shape and required extras); the rules are defined in
+[`protocol/merchant-api.md`](protocol/merchant-api.md#client-side-validation).
+Format checks (phone length, e-mail, ...) stay with the gateway on purpose so the
+SDK cannot drift from it.
+
+### Next steps
+
+Queries, idempotent retries and webhook verification are covered by the platform
+documentation at <https://docs.deepayment.com>; its examples map one to one onto this
+SDK. The wire protocol is in
+[`protocol/webhook.md`](protocol/webhook.md) and
+[`protocol/merchant-api.md`](protocol/merchant-api.md). Key points:
+
+- After a create timeout, query by `merchantOrderNo` first instead of sending a
+  new order; a deliberate retry repeats the same call with the same `merchantOrderNo`.
+- For webhooks, pass the method, path, headers and the **raw, unparsed body bytes**
+  to `client.parse_payment_webhook(method=, path=, headers=, body=)`; the SDK checks
+  the digest, event id, time window and Ed25519 signature. Return 2xx once processed
+  and deduplicate by `eventId`.
+
+## Amounts
+
+Amounts, fees and rates in requests, responses, webhooks, balances, rates and
+receipts are **always decimal strings** such as `"100.00"`. Never use floats.
+
+## Order status
+
+There are exactly six external statuses: `PENDING` `PROCESSING` `SUCCEEDED`
+`FAILED` `EXPIRED` `CANCELED`.
+
+## Troubleshooting
+
+| Situation | Action |
+| --- | --- |
+| Create request timed out | Query by `merchantOrderNo`; do not send a new order |
+| Deliberate retry | Call the same method again with the same `merchantOrderNo` and identical parameters; the SDK regenerates the nonce on every request |
+| Signature rejected | Check the server clock, the access key, and that the merchant private key matches the public key registered with the platform |
+| Body decryption failed | Check that `platform_body_key_id` and the public key belong to the current environment |
+| Webhook signature rejected | Check that the webhook key set contains the `keyid` from the header |
+
+## Tests
+
+```
+python -m pip install -e '.[dev]'
+python -m pytest -q
+```
+
+The tests assert directly against the [`protocol/testdata`](protocol/testdata/)
+vectors: `Signature-Input`, the signature base and the signature value are compared
+byte for byte, and body encryption is verified by opening ciphertext produced by
+the reference implementation.

deepayment-0.1.0/deepayment/__init__.py

@@ -0,0 +1,52 @@
+"""Python SDK for the merchant open API.
+
+Only business methods, DTOs, webhook verification and error types are public.
+Signing, digest and body envelope internals live in _protocol / _request and
+are not exported.
+"""
+
+from .client import Client
+from .errors import (
+    APIError,
+    ConfigError,
+    RequestError,
+    ResponseError,
+    ResponseTooLargeError,
+    SDKError,
+    TransportError,
+    WebhookError,
+)
+from .types import (
+    Balance,
+    CreatePaymentReq,
+    CreatePayoutReq,
+    EXTERNAL_STATUSES,
+    Failure,
+    OrderAction,
+    PaymentOrder,
+    PaymentWebhook,
+    PayoutOrder,
+    PayoutReceipt,
+    PayoutWebhook,
+    STATUS_CANCELED,
+    STATUS_EXPIRED,
+    STATUS_FAILED,
+    STATUS_PENDING,
+    STATUS_PROCESSING,
+    STATUS_SUCCEEDED,
+    USDRate,
+)
+
+__version__ = "0.1.0"
+
+__all__ = [
+    "Client",
+    "CreatePaymentReq", "CreatePayoutReq",
+    "PaymentOrder", "PayoutOrder", "PayoutReceipt", "Balance", "USDRate",
+    "PaymentWebhook", "PayoutWebhook", "OrderAction", "Failure",
+    "SDKError", "ConfigError", "RequestError", "APIError",
+    "ResponseError", "ResponseTooLargeError", "TransportError", "WebhookError",
+    "STATUS_PENDING", "STATUS_PROCESSING", "STATUS_SUCCEEDED",
+    "STATUS_FAILED", "STATUS_EXPIRED", "STATUS_CANCELED", "EXTERNAL_STATUSES",
+    "__version__",
+]