> 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/guides/status-page.md). # Status Page React to deploys, comments, and external events with workflows that run on the platform. The SEB Status Page provides a public, real-time overview of the operational health of the SEB Ecommerce Payment Gateway and its related services. The Status Page is publicly available at: [**https://status.ecommerce.sebgroup.com**](https://status.ecommerce.sebgroup.com/) We recommend bookmarking the Status Page and making it part of your standard operational and support procedures. Use the Status Page to determine whether payment processing issues are caused by a known platform incident, planned maintenance, or an unavailable external service before investigating your own integration. {% hint style="info" %} No Merchant Portal authentication is required to access the Status Page. {% endhint %} {% hint style="info" %} The Status Page reports the operational health of platform services. It does **not** display the status of individual payments, orders, merchant accounts, or API requests. {% endhint %} *** ## Platform Status The Status Page provides a real-time overview of the operational status of the core SEB Ecommerce Payment Gateway services. Core platform components include: * Unified Merchant API * Merchant Portal * Hosted Checkout Each component displays: * Current operational status * Historical availability * Uptime for the previous 30 days *** ## Payment Methods The Status Page reports the operational availability of the payment services supported by the **SEB Ecommerce Payment Gateway**. Depending on the services enabled for your merchant account, this may include: * Card Processing * Apple Pay * Google Pay * Click to Pay * PayPal Monitoring these components helps merchants quickly determine whether an issue affects a specific payment service or the payment platform as a whole. {% hint style="info" %} The availability of a payment service applies only to the corresponding component displayed on the Status Page. For example, an issue affecting **Apple Pay** does not necessarily affect **Card Processing**, **Google Pay**, or other payment services. {% endhint %} *** ## Bank APIs For **Pay by Bank**, the Status Page displays the operational availability of each participating bank's Open Banking API. Each bank is monitored and reported independently, allowing merchants to quickly determine whether a specific bank is currently available. If a participating bank is reported as unavailable, customers may not be able to complete Pay by Bank payments using that bank. Other participating banks and payment methods may continue to operate normally. {% hint style="info" %} The availability of each Bank API depends on the participating bank's own systems and Open Banking infrastructure. SEB monitors and reports the connectivity between the SEB Ecommerce Payment Gateway and each participating bank but does not control or manage the operational availability of external banking services. {% endhint %} {% hint style="info" %} The Status Page reports the operational availability of each participating bank's Open Banking API only. It does not display the status of individual payments, customer authentication sessions, or services that are outside the SEB Ecommerce Payment Gateway. {% endhint %} *** ## Status Indicators Each monitored component is assigned one of the following operational statuses. | Status | Description | | ----------------------- | ---------------------------------------------------------------------- | | **Operational** | The service is operating normally. | | **Partial Degradation** | Some functionality may be affected, but the service remains available. | | **Major Degradation** | Significant service disruption affecting normal operation. | A status applies only to the component beside which it is displayed. For example, an unavailable Open Banking connection does not necessarily affect card payments, Hosted Checkout, or the Merchant Portal. *** ## Incidents and Maintenance The Status Page publishes operational information about: * Service incidents * Scheduled maintenance * Planned releases * Completed releases * Resolved incidents Review planned maintenance before the scheduled maintenance window to understand whether your payment flows, integrations, or operational processes may be affected. *** ## How to Use the Status Page Before investigating your own integration: 1. Open the Status Page. 2. Check the component or payment method related to the issue. 3. Review any active incidents or scheduled maintenance. 4. Continue troubleshooting your own integration if no relevant platform issue is reported. Examples: | Issue | Check | | ------------------------------ | ------------------------------------------------ | | API request failures | Unified Merchant API | | Merchant Portal unavailable | Merchant Portal | | Hosted Checkout unavailable | Hosted Checkout | | Card payment issues | Payment Cards | | Apple Pay or Google Pay issues | Corresponding payment method | | Pay by Bank issues | Pay by Bank and the customer's selected Bank API | *** ## During an Incident If a relevant service incident is reported: * Continue relying on payment callbacks and payment status updates. * Do not fulfil or cancel orders based solely on the public service status. * Avoid asking customers to repeat payments until the original payment status has been confirmed. * Offer alternative payment methods where appropriate. * Record Payment IDs and timestamps if support assistance is required. {% hint style="warning" %} The payment status returned by the gateway remains the source of truth for every individual transaction. {% endhint %} *** ## Status History The Status Page displays current service information together with historical availability for a rolling period of **three months**. Historical information can help merchants: * Review previous incidents. * Compare incidents with application logs. * Review completed maintenance activities. * Support operational investigations. *** ## Merchant Best Practices We recommend that merchants: * Bookmark the Status Page. * Check platform status before investigating integration issues. * Monitor their own application, callback processing, and API responses. * Keep alternative payment methods available whenever possible. * Use idempotent request processing. * Reconcile pending transactions after service disruptions. * Review planned maintenance before major business events. *** ### Frequently Asked Questions #### Do I need to sign in to view the Status Page? No. The Status Page is publicly accessible and does not require Merchant Portal authentication. #### Does Operational mean that my integration is working correctly? Not necessarily. It means that no known issue is reported for the relevant service component. Your own API credentials, endpoints, network, callback processing, or merchant configuration may still require investigation. #### Can I use the Status Page to check whether a payment succeeded? No. Use the payment status returned by the gateway, callback notifications, or the Merchant Portal to check an individual payment. #### Why is one bank unavailable while other Pay by Bank payments still work? Each participating bank provides its own Open Banking interface. A disruption can affect one ASPSP connection without affecting other banks or payment methods. #### Should I ask the customer to pay again during an incident? First check the original payment’s current status. The payment may have completed even if the customer saw an error or your application did not receive the expected response. Create a new payment only after confirming that the original attempt did not complete. #### How much history is available? The public Status Page displays historical entries for a rolling period of three months. #### Does the Status Page replace Release Notes? No. The Status Page communicates operational incidents, maintenance, and release completion. Release Notes explain merchant-facing functional and technical changes in more detail. #### What should I do when no incident is shown? Continue troubleshooting your integration. Check the returned API error, credentials, environment, merchant configuration, callback endpoint, application logs, and network access. Contact SEB Support if the issue remains unresolved. --- # 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/guides/status-page.md?ask=&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.