> 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/payment-method/card-payments.md).

# Card Payments

### Overview

Merchants can accept card payments through the gateway, integrating with acquiring banks via the Acquirer API provided and supported by gateway. Transactions are processed using standardized messaging protocols, enabling secure communication between merchants and financial institutions.

The E-Commerce Payment Gateway supports card payment processing for major international card schemes, including **Visa**, **Mastercard**, **Diners**, **American Express**, **JCB**, **UnionPay** (UPI) and local such as **PROSTIR** (NPS) or **Borica** (Bulgaria) and etc.. The solution enables to offer merchants a secure, reliable, and fully compliant acquiring service for card-based transactions.

### Transaction Processing

The payment processing flow managed by the E-Commerce Payment Gateway covers the authorization and transaction routing, ensuring secure and efficient forwarding of payment instructions to acquiring systems for subsequent clearing and settlement processing.

Transactions are securely routed to the configured acquiring platform. EGW integrates with multiple acquiring platforms and adapts transaction messages to the format required by each integration. Where applicable, this may include mapping to ISO 8583. This seamless interoperability guarantees efficient communication between the gateway and the acquiring infrastructure, enabling to process transactions with high reliability, minimal latency, and full compliance with industry protocols and standards.

For Payment Facilitator transactions, EGW can pass Payment Facilitator and sub-merchant data to the acquiring system as required by the acquiring setup and applicable card scheme rules.

### Card Payment Lifecycle

A card payment may be processed as a final authorization or as a pre-authorization, depending on the merchant configuration and the use case.

With a final authorization, the payment is authorized and submitted for capture as part of the payment flow. With a pre-authorization, the amount is first reserved on the card. The merchant can capture the payment later, for the full or a partial amount, or cancel the pre-authorization. If it is not captured or cancelled, it may expire according to the applicable acquirer and card scheme rules.

After authorization, EGW reports the transaction status through the Merchant Portal, API, and configured notifications. Merchants should use the latest transaction status returned by EGW to determine the outcome of a payment and whether further action is required. An authorization does not by itself confirm that funds have been captured or settled.

### Security and Authentication

Security measures such as 3D Secure (3DS) authentication and tokenization ensure compliance with regulatory requirements while minimizing fraud risks.

The solution includes support for 3D Secure 2.x authentication, enabling Strong Customer Authentication (SCA) in compliance with PSD2 and other applicable regulations. This reduces the risk of fraud and improves transaction approval rates by providing frictionless authentication for low-risk transactions and step-up authentication when required.

### Tokenization and Stored Credentials

To ensure the highest level of security and compliance, the Tieto E-Commerce Payment Gateway applies tokenization to all card payments by default, regardless of whether merchants actively use tokenized payments in their processes. Sensitive cardholder data is never stored or exposed within the platform. Instead, all card details are immediately replaced with secure, non-sensitive tokens generated by the EGW solution.

This approach ensures that no card data is accessible to users of the Merchant or Administration Portals, supporting full PCI DSS compliance and minimizing the risk of data breaches.

Tokenized credentials allow merchants to support recurring payments and one-click transactions, improving customer convenience and enabling higher issuer approval rates. They can be used for Customer-Initiated Transactions (CIT), including one-click payments, and Merchant-Initiated Transactions (MIT), such as recurring payments or subscriptions, enabling seamless and secure repeat payment experience.


---

# 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/payment-method/card-payments.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.
