> 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/moto.md).

# MOTO

EGW supports MOTO transactions, enabling merchants to accept card payments that are initiated via phone calls, email, or manually keyed-in orders, typically in environments like call centers or back offices.

This functionality allows merchants to securely capture payments without the customer being physically present or interacting with an online checkout interface.

## **Core Capabilities**

* Manual Payment Entry Interface -  Merchants can enter customer card details via a secure form within the Merchant Portal or via API.
* PCI DSS Compliance - All MOTO transactions are handled in a PCI-compliant environment. Sensitive card data is processed securely with no storage of raw cardholder information on merchant systems.
* Transaction Flagging - MOTO payments are automatically flagged with the appropriate indicator (MOTO e-commerce flag) for proper acquirer and scheme handling.
* Fraud Risk Mitigation - While 3D Secure is typically not used in MOTO, EGW supports fraud prevention strategies such as:
  * Rule-based risk checks
  * Block/Allow list validation
  * Velocity checks and amount limits
* Multi-Currency Support - MOTO payments can be accepted in any supported currency, just like online payments.
* Merchant Role Management - Access to MOTO features can be restricted to authorized users only through granular permission settings in the Merchant Portal.

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td>Customer places an order over the phone and provides card details for processing.</td></tr><tr><td>Merchant processes subscription or invoice payments initiated from customer email requests.</td></tr><tr><td>Call center teams take orders remotely using secure merchant-side tools.</td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.ecomm.api.tietoevry.com/features/moto.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.