Skip to main content
The native SDKs are deliberately tiny. Each is a single file, standard-library only, no package-manager install needed. They cover the three things every integration does: create a hosted checkout, verify a webhook, and check a payment’s status.

​
Available SDKs

LanguageWhat it coversSource
GoHTTP server integration with the standard librarynative-go
PHPAny PHP application without Composernative-php
PythonAny Python web app without pipnative-python
RustAny Rust HTTP server (stdlib only, no crates)native-rust

​
What you get

Each SDK exposes the same three methods:
  • create_checkout(amount, currency, label, network) returns a hosted-checkout URL.
  • verify_payment(token) polls the gateway for status.
  • verify_webhook(raw_body, signature_header, secret) checks an inbound webhook’s HMAC and timestamp.

​
Python example

from algovoi import AlgoVoi

client = AlgoVoi(
    api_base="https://api1.ilovechicken.co.uk",
    api_key="algv_…",
    tenant_id="…",
    webhook_secret="algvw_…",
)

# Create a checkout
link = client.create_checkout(amount=5.00, currency="USD", label="Order #1234")
print(link.checkout_url)

# Later, verify the inbound webhook in your Flask handler
def webhook():
    raw = request.get_data()
    sig = request.headers.get("X-AlgoVoi-Signature", "")
    event = client.verify_webhook(raw, sig)
    if not event:
        return "", 401
    # Process event["data"]["tx_id"], event["data"]["amount_microunits"], etc.
    return "", 200

​
When to use a native SDK

  • Your platform doesn’t have a dedicated adapter
  • You don’t want to add a dependency
  • You’re integrating from a serverless function with cold-start budget concerns
For platforms we already cover, the framework adapters, e-commerce modules, and no-code platforms save you the boilerplate.

​
See also