> For the complete documentation index, see [llms.txt](https://docs.ecommerce.seb.ee/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecommerce.seb.ee/getting-started/integration-checklist.md).

# Integration checklist

This guide walks you through the complete integration process for the SEB Ecommerce Payment Gateway — from merchant onboarding to processing your first live transaction.

## Environment Reference

The **SEB Ecommerce Payment Gateway** provides separate Sandbox and Production environments together with supporting merchant services.

| Service                          | Address                                   |
| -------------------------------- | ----------------------------------------- |
| **Merchant Portal**              | `merchantportal.ecommerce.sebgroup.com`   |
| **Merchant Documentation**       | `docs.ecommerce.sebgroup.com`             |
| **Merchant API — Sandbox**       | `sandbox.api.ecommerce.sebgroup.com`      |
| **Merchant API — Production**    | `api.ecommerce.sebgroup.com`              |
| **Hosted Checkout — Sandbox**    | `sandbox.checkout.ecommerce.sebgroup.com` |
| **Hosted Checkout — Production** | `checkout.ecommerce.sebgroup.com`         |
| **Service Status**               | `status.ecommerce.sebgroup.com`           |

{% hint style="info" %}
Sandbox and Production are separate environments. Always use the API endpoint, credentials, shop configuration, and related URLs for the environment in which you are operating.
{% endhint %}

***

## Step 1 — Complete Merchant Onboarding

Before starting your integration, ensure that your merchant onboarding with SEB has been completed.

#### What You Need

* Signed Merchant Agreement
* Activated Merchant Portal account
* Access to Sandbox Mode
* Required services and payment methods enabled according to your merchant agreement

If you have not yet completed onboarding, see [**Quick Start**.](/getting-started/quickstart.md)

***

## Step 2 — Choose Your Integration

Select the integration method that best matches your ecommerce platform, technical architecture, and business requirements.

Available integration options may include:

* [Unified Merchant API](/integration/merchant-api.md)
* [API Client SDK](/integration/api-client-sdk.md)
* [Hosted Checkout](/integration/hosted-checkout.md)
* [Web Plugins](/integration/web-plugins.md)
* [Mobile SDKs](/integration/mobile-sdk.md)

Review the requirements and capabilities of your selected integration method before starting development.

{% hint style="info" %}
Your PCI DSS responsibilities depend on the selected integration method and how your solution handles cardholder data.
{% endhint %}

***

## Step 3 — Configure Sandbox

After activating your Merchant Portal account, you will enter [**Sandbox Mode**](/guides/sandbox/using-sandbox-mode.md) **by default**.

Before starting development:

* Verify or create your Sandbox Shop.
* Enable the required payment methods and services.
* Obtain the API credentials for the Sandbox Shop.
* Configure the **Home URL**.
* Configure the **Callback URL**, where applicable.
* Review the payment authorization and capture configuration applicable to your integration.

Each Sandbox Shop has its own API credentials. Always use the credentials associated with the shop processing your test transactions.

***

## Step 4 — Develop Your Integration

Implement your selected payment solution according to the corresponding integration documentation.

Depending on your integration method, implementation may include:

* Authentication
* Payment creation
* Customer redirect handling
* Payment status handling (see Payment Statuses [Cards](/payment-methods/cards/payment-statuses.md) and [Pay by Bank](/payment-methods/pay-by-bank/payment-statuses.md))
* Callback / webhook processing
* Error handling
* Order status management
* Refunds and other payment operations

***

## Step 5 — Test Your Integration

Validate your integration in [**Sandbox Mode**](/guides/sandbox/using-sandbox-mode.md) before processing live customer transactions.

#### Core Payment Scenarios

Validate, where applicable:

* Successful payments
* Declined or failed payments
* Customer cancellations
* Abandoned payment journeys
* Authentication scenarios
* Retry after failure

#### Integration & Order Handling

Verify that:

* Payment statuses are handled correctly (see Payment Statuses [Cards](/payment-methods/cards/payment-statuses.md) and [Pay by Bank](/payment-methods/pay-by-bank/payment-statuses.md)).
* Callback or webhook notifications are received and processed.
* Customer redirects and returns are handled correctly.
* Duplicate notifications and requests are handled idempotently.
* Orders are fulfilled only after the required final payment status is confirmed.
* Payment IDs are stored and can be matched with transactions in the Merchant Portal.

#### Payment Operations

Where applicable to your configuration, validate:

* Refund
* Partial refund
* Authorization and capture
* Partial capture
* Cancellation or reversal

#### Payment Methods

Validate all payment methods that you intend to use and that are enabled for your **Sandbox Shop**.

Use [**Test Data**](/guides/sandbox/test-data.md) and [**Test Scenarios**](/guides/sandbox/test-scenarios.md) for the recommended Sandbox validation process.

{% hint style="info" %}
Testing and validation of your integration are your responsibility. The customer browser return alone must not be used as confirmation that a payment has completed. Use the confirmed gateway payment status as the source of truth.
{% endhint %}

***

## Step 6 — Prepare for Live

When your integration has been tested and you are ready to process live customer transactions:

1. Confirm that Live Mode is available for your merchant account. If Live access is not yet enabled, follow the agreed SEB activation process ([*Go-live checklist*](/getting-started/go-live-checklist.md)).
2. Switch to **Live Mode** in the Merchant Portal.
3. Review or configure your Production Shop.
4. Obtain the API credentials for your Production Shop.
5. Configure your application to use the Production endpoints and credentials.
6. Verify your Production **Home URL** and **Callback URL**.
7. Verify that all required Production payment methods and services have been activated.
8. Review your Hosted Checkout configuration and branding, where applicable.

{% hint style="info" %}
Do not use Sandbox credentials or Sandbox endpoints in Live. Live configuration and credentials are managed separately from Sandbox.
{% endhint %}

***

## Step 7 — Go Live

After your Live configuration is ready, begin processing live customer transactions.

Closely monitor your first transactions and verify that:

* Payments reach the expected final statuses (see Payment Statuses [Cards](/payment-methods/cards/payment-statuses.md) and [Pay by Bank](/payment-methods/pay-by-bank/payment-statuses.md)).
* Callback / webhook notifications are received and processed correctly.
* Orders are updated correctly.
* Payment amounts and currencies match your orders.
* Transactions are visible in **Merchant Portal → Orders**.
* Refunds and other required payment operations work as expected.
* Settlement and reconciliation processes match your business records.

For ongoing service availability, use the **SEB Status Page** at `status.ecommerce.sebgroup.com`.

### Need Help?

If you experience unexpected behaviour or need help with your integration:

* Review the relevant documentation for your integration, payment method, or feature.
* Use the **AI Assistant** available on the Documentation Portal to ask questions about the documentation and find relevant guidance.

<p align="center"><button type="button" class="button primary" data-action="ask" data-icon="gitbook-assistant">Ask a question…</button></p>

* If you cannot resolve the issue using the documentation or AI Assistant, contact **SEB Support**.

When contacting SEB Support about a transaction or technical issue, provide relevant information such as the **Payment ID**, timestamp, affected service, and error details where available.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ecommerce.seb.ee/getting-started/integration-checklist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.