Teggen Payments documentation
Teggen Payments lets your business accept payments through a hosted checkout page, using a small REST API.
The integration is three steps:
- Create a payment session on your server.
- Redirect your customer to the hosted checkout page.
- Confirm the result on your server, by webhook or by reading the payment back.
Card data never touches your systems.
Start here
| Page | What it covers |
|---|---|
| Sandbox quickstart | Your first test payment, end to end |
| Authentication and environments | API keys, scopes, sandbox versus live |
| Accepting payments | The full lifecycle: sessions, checkout, statuses, idempotency, return URLs |
Integrate
| Page | What it covers |
|---|---|
| Webhooks | Receiving signed events and verifying them correctly |
| Refunds | Requesting refunds and tracking their state |
| Fulfillment tracking | Submitting carrier tracking against captured payments |
| Error handling | The error envelope and every code you can receive |
| Going live | The review step between sandbox and real money |
Plugins
| Page | What it covers |
|---|---|
| TeggenPay for WooCommerce | Install, connect, and run a WooCommerce store on Teggen |
API reference
Start at the API reference overview for conventions, the base URL and the machine-readable OpenAPI document. Per resource:
| Resource | Page |
|---|---|
| Payment sessions | /api-payment-sessions |
| Payments | /api-payments |
| Refund requests | /api-refunds |
| Balances | /api-balances |
| Settlements | /api-settlements |
| Stores | /api-stores |
| Fulfillments | /api-fulfillments |
| Store integrations | /api-integrations |
| Store order sync | /api-store-orders |
| Webhook monitoring | /api-webhook-endpoints |
| Events | /api-events |
| Disputes | /api-disputes |
| API keys | /api-keys |
| Changelog and versioning | /changelog |
Support
For questions, allowlist changes, or going live, contact your Teggen onboarding or support contact.