> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/digital-river-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/digital-river-api/integration-options/checkouts/creating-checkouts/initiating-a-charge.md).

# Initiating a charge

When [creating ](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/checkouts#checkouts-1)or [updating a checkout](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/checkouts#checkouts-id-1) or [creating an Invoice](https://docs.digitalriver.com/digital-river-api-reference/2021-12-13/invoices#invoices-1), you can use the `chargeType` parameter to tell Digital River whether you expect to use the [payment source](/digital-river-api/payments/payment-sources.md) for a [customer-initiated](#customer-initiated), [merchant-initiated](#merchant-initiated), or [mail/telephone-initiated](#mail-order-telephone-order) transaction.

## Customer initiated

In this case, the cardholder actively participates in the transaction. A `customer-initiated` transaction is the most common charge type, representing the majority of online checkouts or invoices. During these transactions, the [customer provides payment details](/digital-river-api/payments/payment-sources/using-the-source-identifier.md#charging-a-single-use-source) at the time of checkout or invoice or uses [stored payment information](/digital-river-api/payments/payment-sources/using-the-source-identifier.md#attaching-a-source-to-a-customer).

| Can a CVV be used? | Can 3DS measures be used? |
| ------------------ | ------------------------- |
| Yes                | Yes                       |

## Merchant initiated

A `merchant_initiated` transaction is submitted using stored payment details without the cardholder's active participation during the checkout or invoice process. This charge type can only occur when an agreement allows the client to initiate payments on behalf of their customers.

Since Digital River is the [authorized reseller of record](/digital-river-api/readme.md), we initiate and process the transaction on your behalf. You, in turn, are acting on the behalf of your customer.

[Subscription renewals](/digital-river-api/integration-options/checkouts/subscriptions/subscription-information-1.md#creating-and-renewing-subscriptions) and automated payments for water, sewer, gas, or electric utilities are common examples of this charge type.

| Can a CVV be used? | Can 3DS measures be used? |
| ------------------ | ------------------------- |
| No                 | No                        |

## Mail order/telephone order

A Mail Order/Telephone Order (MOTO) is a payment card transaction initiated by mail, fax, or phone. In these `moto` transactions, customers provide the merchant with their payment details by mail, fax, or telephone. By supplying this information, the customer authorizes the merchant (who, in turn, authorizes Digital River) to process the transaction.

Additionally, when `chargeType` is set to `moto`, the user is only presented with payment methods that support this type of transaction. Whether your integration displays payment methods using [Drop-in payments](/digital-river-api/payments/payment-integrations-1/drop-in.md) or [DigitalRiver.js with elements](/digital-river-api/payments/payment-integrations-1/digitalriver.js/quick-start.md) it is true.

| Can a CVV be used? | Can 3DS measures be used? |
| ------------------ | ------------------------- |
| Yes                | No                        |


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.digitalriver.com/digital-river-api/integration-options/checkouts/creating-checkouts/initiating-a-charge.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.