SDKs
Open Pay provides official SDKs for five languages plus a CLI tool. Every SDK handles HMAC-SHA256 request signing automatically, so you never have to compute signatures manually.TypeScript
@openpay/sdk for Node.js and edge runtimesGo
openlankapay-go-sdk for backend servicesPython
openpay-sdk with async httpx supportPHP
openpay/sdk via ComposerJava
com.openpay:openpay-sdk for JVM applicationsCLI
openpay command-line toolCommon Features
All SDKs share the same capabilities:| Feature | Description |
|---|---|
| Create Payments | Generate payment requests with amount, currency, and metadata |
| Checkout Sessions | Create hosted checkout pages with success/cancel URLs |
| Webhook Verification | Verify ED25519-signed webhook payloads |
| HMAC Authentication | Automatic request signing with your API key and secret |
| Error Handling | Typed errors with status codes and descriptive messages |
| Retry Logic | Automatic retries with exponential backoff for transient failures |
Authentication
Every SDK uses HMAC-SHA256 to sign requests. You provide your API key (public identifier) and API secret (signing key), and the SDK handles the rest. The signature is computed as:| Header | Value |
|---|---|
x-api-key | Your API key (ak_live_xxx) |
x-timestamp | Unix timestamp in milliseconds |
x-signature | HMAC-SHA256 hex digest |
Get your API key and secret from the Merchant Portal under Integrations.
Quick Comparison
- TypeScript
- Go
- Python
- PHP
- Java
API Base URL
All SDKs default to the production API:baseUrl option during client initialization if you are targeting a different environment.