tbc-payments
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_paymentreturnsNoneafter a successful200.complete_paymentreturnsCompletionResult.sandbox=Trueuseshttps://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
Metadata
Release files for tbc-payments 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| tbc_payments-0.3.0.tar.gz | 21.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tbc_payments-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 38.5 kB
Release files / tbc_payments-0.3.0.tar.gz
| Download URL | tbc_payments-0.3.0.tar.gz |
|---|---|
| Size | 21.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
df7cb09aaee61604d8fc48e8482ca10a1761f8422c9c615905e1f3df70d80be0
|
|
BLAKE2b-256 checksum How to use checksums |
cb0cbd03ed915f2372084b82949464ca16579239a6a4cee9005d0b912674aa0d
|
| 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 logRelease files / tbc_payments-0.3.0-py3-none-any.whl
| Download URL | tbc_payments-0.3.0-py3-none-any.whl |
|---|---|
| Size | 17.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1e5385082b71290ea7c0042f0950f649cb5b8247cf063d7fdaf6bbc07f80f1a0
|
|
BLAKE2b-256 checksum How to use checksums |
a10b0db1501faeb4ab14d9d9c900f545ee5a44b5b310350ad88cc21edc9bc50b
|
| 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