Skip to main content

tbc-payments

PyPI Python CI Documentation License

tbc-payments is a small, typed Python client for TBC Checkout. It helps a backend create a checkout session, redirect the customer to TBC's payment page, and later verify or manage the payment.

It has synchronous and asynchronous clients with the same API. The package manages access tokens and HTTP connections; it never handles card details.

Full guides for callbacks, FastAPI, Django, recurring payments, sandbox operations, and the API are available in the documentation.

What it supports

  • Creating and looking up Checkout payments.
  • Cancelling payments and completing pre-authorizations.
  • Creating and deleting recurring-payment registrations.
  • TBC Installment requests.
  • Production and sandbox URLs.
  • Typed models, structured API errors, timeouts, and conservative retries.

Installation

pip install tbc-payments

Python 3.10 or newer is required.

Create a payment

from tbc_payments import Amount, PaymentMethod, PaymentRequest, TBCClient

payment_request = PaymentRequest(
    amount=Amount("49.90"),
    return_url="https://shop.example.com/payments/return",
    callback_url="https://shop.example.com/webhooks/tbc",
    merchant_payment_id="order-1842",
    methods=(PaymentMethod.CARD, PaymentMethod.APPLE_PAY),
)

with TBCClient("api-key", "client-id", "client-secret") as tbc:
    payment = tbc.create_payment(payment_request)

redirect_url = payment.approval_url

Redirect the customer to redirect_url. A merchant_payment_id should be unique in your system so an ambiguous request can be reconciled safely.

Check the result

Treat the callback as a notification, not as confirmation that an order is paid. Return HTTP 200 promptly, then fetch the payment from TBC and fulfil the order only once.

payment = tbc.get_payment(callback_payload["PaymentId"])
if payment.status == "Succeeded":
    fulfil_order_once(payment.pay_id)

Async

from tbc_payments import Amount, AsyncTBCClient, PaymentRequest

async with AsyncTBCClient("api-key", "client-id", "client-secret", sandbox=True) as tbc:
    payment = await tbc.create_payment(
        PaymentRequest(Amount("1.00"), "https://shop.example.com/payments/return")
    )

FastAPI and Django

Optional adapters validate callback request bodies without taking ownership of your application's client lifecycle or order database:

pip install "tbc-payments[fastapi]"
# or
pip install "tbc-payments[django]"

See the framework guides and runnable examples. A callback is only a notification: fetch the payment from TBC and fulfil its order idempotently before returning HTTP 200.

Installments and recurring payments

Use PaymentMethod.INSTALLMENT with products whose total matches the payment amount:

from tbc_payments import InstallmentProduct, PaymentMethod

request = PaymentRequest(
    amount=Amount("100.00"),
    return_url="https://shop.example.com/payments/return",
    methods=(PaymentMethod.INSTALLMENT,),
    installment_products=(InstallmentProduct("50.00", 2, "Coffee maker"),),
)

For saved cards, enable save_card=True when creating the initial payment and store the returned recurring_id. Call execute_recurring_payment only after your business flow has established the necessary customer consent.

Behaviour worth knowing

  • Amounts may have at most two decimal places. Values are validated rather than silently rounded.
  • Tokens are refreshed before expiry. A failed read may be retried; money-moving requests are not retried automatically.
  • cancel_payment returns None after a successful 200. complete_payment returns CompletionResult.
  • sandbox=True uses https://test-api.tbcbank.ge/v1.

Development

python -m pip install -e '.[dev]'
pre-commit install
pytest
ruff check .
ruff format --check .
mypy
bandit -c pyproject.toml -r src
pip-audit

Build the local documentation site with:

python -m pip install -e '.[docs]'
mkdocs serve

See CONTRIBUTING.md and SECURITY.md for contribution and vulnerability-reporting guidance.

License

MIT

Metadata

Release files for tbc-payments 0.3.2

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

Source distribution (sdist)

Source distribution for tbc-payments 0.3.2
File Size Uploaded
tbc_payments-0.3.2.tar.gz 24.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for tbc-payments 0.3.2
File Interpreter ABI Platform
tbc_payments-0.3.2-py3-none-any.whl Python 3 none any Details

Total release size: 41.6 kB

Release files / tbc_payments-0.3.2.tar.gz

Download URL tbc_payments-0.3.2.tar.gz
Size 24.5 kB
Tags Source
SHA-256 checksum
How to use checksums
b825ae4ff1fa46a9ce457bb53e963e174c428ba21a127e8559d2476790a71a42
BLAKE2b-256 checksum
How to use checksums
8f43aba832082e6d2c33cbe4ae366acb17e85aea1ae87c415bdb1a10ebb36e60
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Oct 2, 2026.

Transparency log

Release files / tbc_payments-0.3.2-py3-none-any.whl

Download URL tbc_payments-0.3.2-py3-none-any.whl
Size 17.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
81f0e25801e8f9b77f8925a1f6d75eecf971717a7ad9290b114c58c6184348cc
BLAKE2b-256 checksum
How to use checksums
27a656a1ddc3cf1de9cc2ff3bca095ec011bf635fd515db4924137f75b20d9b7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Oct 2, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.2 This release

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.0

2 release files

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