> 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/payment-methods/cards.md).

# Cards

Accept secure online card payments using the SEB Ecommerce Payment Gateway.

## Payment Cards

The SEB Ecommerce Payment Gateway enables merchants to securely accept online card payments through internationally recognized card schemes.

Our platform supports the complete card payment ecosystem, including secure authentication, payment authorization, [tokenization](/payment-methods/cards/tokenization.md), [stored credentials](/payment-methods/cards/stored-credentials.md), [refunds](/features/refunds.md), and [recurring payments](/features/recurring-payments-and-subscriptions.md).

Whether you are integrating a [Hosted Checkout](/integration/hosted-checkout.md), or [Merchant API](/integration/merchant-api.md) solution, the gateway provides a secure payment experience and is PCI DSS Level 1 compliant.

***

### Supported Card Schemes

Currently supported:

| Card Scheme | Supported |
| ----------- | :-------: |
| Visa        |     ✅     |
| Mastercard  |     ✅     |

Additional card schemes may become available in future releases.

***

### Key Capabilities

The gateway supports:

* [Secure online card payments](/payment-methods/cards/card-payment-lifecycle.md)
* [EMV® 3-D Secure authentication](/payment-methods/cards/emv-r-3-d-secure-emv-3ds.md)
* [Authorization and Capture](/payment-methods/cards/supported-operations.md)
* [Full and Partial Refunds](/payment-methods/cards/supported-operations.md)
* [Reversals](/payment-methods/cards/supported-operations.md)
* [Tokenization](/payment-methods/cards/tokenization.md)
* [Stored Credentials](/payment-methods/cards/stored-credentials.md)
* [Customer-Initiated Transactions (CIT)](/payment-methods/cards/stored-credentials/customer-initiated-transactions-cit.md)
* [Merchant-Initiated Transactions (MIT)](/payment-methods/cards/stored-credentials/merchant-initiated-transactions-mit.md)
* [Recurring Payments](/features/recurring-payments-and-subscriptions.md)
* [One-Click Payments](/features/one-click-payments.md)

Availability depends on your merchant agreement and enabled services.

***

### Integration Options

Card payments can be integrated using:

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

Choose the integration method that best matches your business and technical requirements.


---

# 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/payment-methods/cards.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.