Skip to main content

capo-payment-cryptography-data: typed, async Python SDK for AWS Payment Cryptography Data

capo-payment-cryptography-data is a typed Python SDK for AWS Payment Cryptography Data. It has an async client, AsyncPaymentCryptographyDataClient, for asyncio and trio, and a sync client, PaymentCryptographyDataClient, with the same methods. Requests and responses are typed with TypedDicts, so your editor and type checker know every field.

It is part of capo, a community-driven alternative to boto3 and aioboto3, built on its own HTTP stack instead of botocore and generated from the official AWS Smithy models. Documentation: https://capo-sdk.dev/services/payment-cryptography-data/

Installation

pip install capo-payment-cryptography-data

Usage

from capo_payment_cryptography_data import AsyncPaymentCryptographyDataClient


async def main():
    async with AsyncPaymentCryptographyDataClient() as payment_cryptography_data:
        # Example: call the decrypt_data operation
        response = await payment_cryptography_data.decrypt_data()
        print(response["key_arn"])

Error Handling

The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.

from capo_payment_cryptography_data import AsyncPaymentCryptographyDataClient
from capo_payment_cryptography_data.error import AccessDeniedException


async def main():
    async with AsyncPaymentCryptographyDataClient() as payment_cryptography_data:
        try:
            await payment_cryptography_data.decrypt_data()
        except AccessDeniedException as e:
            print(f"Error: {e}")
            print(e.data)  # additional error data

Retrying

The SDK retries failed operations automatically. Retry behaviour follows the Smithy specification: errors are retried based on their is_retryable and is_throttling_error attributes. Throttling errors use a longer base delay. Network-level failures (connection errors and timeouts) are also retried. Non-retryable errors, such as client errors without the @retryable trait, are raised immediately without further attempts.

The number of attempts defaults to 3 and can be changed at the client level via retry_max_attempts, or per call via config_overrides.

from capo_payment_cryptography_data import AsyncPaymentCryptographyDataClient


async def main():
    async with AsyncPaymentCryptographyDataClient() as payment_cryptography_data:
        # Default: 3 attempts for every operation
        response = await payment_cryptography_data.decrypt_data()

        # Override per operation
        response = await payment_cryptography_data.decrypt_data(config_overrides={"retry_max_attempts": 5})

        # Disable retries for this call
        response = await payment_cryptography_data.decrypt_data(config_overrides={"retry_max_attempts": 1})

Metadata

Release files for capo-payment-cryptography-data 0.9.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for capo-payment-cryptography-data 0.9.0
File Size Uploaded Provenance
capo_payment_cryptography_data-0.9.0.tar.gz 131.1 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-payment-cryptography-data 0.9.0
File Interpreter ABI Platform
capo_payment_cryptography_data-0.9.0-py3-none-any.whl Python 3 none any Details

Total release size: 387.0 kB

Release files / capo_payment_cryptography_data-0.9.0.tar.gz

Download URL capo_payment_cryptography_data-0.9.0.tar.gz
Size 131.1 kB
Tags Source
SHA-256 checksum
How to use checksums
9a5e4361c9bbf6fd173db5ab7e5b44f84806f32ccb2366f2f4f1f389804ccde5
BLAKE2b-256 checksum
How to use checksums
fb98d97c34d5a21467319be7dfdf0b80e232d0ce40ae98eab5c7217bd16c8631
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / capo_payment_cryptography_data-0.9.0-py3-none-any.whl

Download URL capo_payment_cryptography_data-0.9.0-py3-none-any.whl
Size 255.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
10622532530eafa16aab82e40b27c1b068aad460f4843b0f051680485eed7ac4
BLAKE2b-256 checksum
How to use checksums
a8f18b048a38d5e0e4d4e0fa63d792b3e5f9e1b5136eec6ab676161b8ca37eb3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for capo-payment-cryptography-data 0.9.0

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

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

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page