Hosted Checkout

Create a checkout session via the Online Payments API and redirect your customer to a Teya-hosted checkout page. The session supports order details, line items, and configurable redirect URLs.

How it works

1 Create checkout session (server)

2 Redirect to session URL

3 Customer completes payment

4 Redirect back + webhook

Full checkout flow with order summary

Supports line items and metadata

Automatic 3DS and error handling

Configurable success/cancel URLs

Before getting started

1. Get merchant credentials

As a partner you take payments on behalf of the merchants you serve. Each merchant's Client ID and Client Secret are delivered to your registrationWebhook when the merchant connects Teya to your platform, along with the store_id and payment_webhook_public_key.

Use client_credentials grant to obtain access tokens

Each merchant store has its own set of credentials

Store credentials securely and never expose them in client-side code

```admonition icon: fas fa-key title: A separate Client ID and Client Secret per merchant content: Unlike POSLink credentials, these aren't shared across your merchant base. Each merchant you serve gets its own Client ID and Client Secret, delivered to your registrationWebhook when they connect - keep each merchant's credentials separate and don't reuse one set across multiple merchants. ``` ```admonition icon: fas fa-user-plus title: Not registered yet? content: Set up your partner account and implement the merchant registration flow first. Teya sends each merchant's credentials to your registration webhook. link: /partners/online-payments/register-merchants ```

2. API URLs

Service	Staging	Production
Online Payments API	`https://api.teya.xyz`	`https://api.teya.com`
OAuth	`https://id.teya.xyz/oauth/v2/oauth-token`	`https://id.teya.com/oauth/v2/oauth-token`
Business Portal	`https://business.teya.xyz`	`https://business.teya.com`

3. Required scopes

Include these as a space-separated string in your OAuth token request:

scope: 'checkout/sessions/create checkout/sessions/id/get refunds/create'

Scope	Description
`checkout/sessions/create`	Create a hosted checkout session
`checkout/sessions/id/get`	Get hosted checkout session by ID
`refunds/create`	Issue a refund for a completed payment

Example responses

POST - Create a checkout session

```json { "session_id": "14411456-79c8-4d8c-8498-f01907093b83", "session_token": "eyJhbGciOiJSUzI1NiJ9...", "session_url": "https://checkout.teya.com/session/14411456-79c8-4d8c-8498-f01907093b83", "session_status": "ACTIVE" } ```

Redirect the customer to session_url. Use session_id to retrieve the session status later.

```admonition icon: fas fa-info-circle title: Info content: Use session_url to redirect the customer to the hosted checkout page. Use session_id to check the session status later.
Note on amount.value: Always in the smallest currency unit - for EUR, 5000 = €50.00. ```

GET - Retrieve a checkout session

```json { "session_id": "14411456-79c8-4d8c-8498-f01907093b83", "session_status": "ACTIVE", "amount": { "value": 5000, "currency": "EUR" }, "type": "SALE", "payment_status": "NONE", "success_url": "https://yoursite.com/success", "cancel_url": "https://yoursite.com/cart" } ```

Error handling

Status	Meaning	What to do
`401`	Invalid or expired token	Re-authenticate using `client_credentials`
`403`	Missing scope	Ensure `checkout/sessions/create` is in your scope list
`409`	Duplicate idempotency key	Use a unique `Idempotency-Key` header for each request
`422`	Invalid request body	Check `amount.value` is in smallest currency unit

Webhooks - Set up webhooks to receive payment notifications
Customize - Branding, checkout messages, and session options
Testing - Test cards and integration checklist
Troubleshooting - Common issues and best practices
API Reference - Full API endpoint documentation

Try it live - Create a Checkout Session

This will create a real checkout session in the Staging environment. You'll need valid Staging credentials before proceeding.

```admonition icon: fas fa-exclamation-triangle title: Staging endpoints shown below content: Before going live, swap:
• api.teya.xyz → api.teya.com
• id.teya.xyz → id.teya.com ```