> For the complete documentation index, see [llms.txt](https://doc.ecomm.api.tietoevry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ecomm.api.tietoevry.com/features/subscription-management.md).

# Subscription Management

EGW supports recurring payment processing for subscription-based services. The merchant’s subscription or billing system manages plans, billing schedules, payment initiation, retries, and customer communication. EGW processes payment requests from the merchant and provides payment status updates.

### Initial Payment and Payment Credentials

The initial payment or mandate setup may require customer consent and authentication, depending on the payment method. For cards, EGW can tokenize payment credentials for future use. Pay by Bank recurring payments are available only when supported by the bank and the configured payment flow.

### Recurring Payment Processing

When a payment is due, the merchant’s system initiates it through the EGW API using the applicable stored credentials or mandate. EGW processes the request and returns the payment status.

Available recurring payment methods depend on the merchant’s configuration, payment method, bank, and market.

### Responsibilities

The merchant’s subscription or billing system is responsible for:

* Managing subscription plans and billing schedules
* Initiating recurring payments
* Deciding whether and when to retry failed payments
* Managing dunning and customer communication
* Updating subscription status based on payment results

EGW processes payment requests and returns results through the API and configured notifications. A successful initial payment does not guarantee approval of future payments.


---

# 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://doc.ecomm.api.tietoevry.com/features/subscription-management.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.
