> For the complete documentation index, see [llms.txt](https://docs.ecwid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecwid.com/guides/payments/process-online-payment-requests/step-3.-initialize-the-transaction-from-payment-provider.md).

# Step 3. Initialize the transaction from payment provider

With all the required details, you can process the transaction.

#### What happens on the storefront

When a customer selects your payment method and clicks the **Go to Payment** button at the checkout, Ecwid redirects a customer from the store checkout to your `paymentUrl`. 

After that, you show the customer a placeholder while processing the initial payment request. Once that part is finished, you have two options:

* If possible, initialize the payment form right on the `paymentUrl` . It reduces the number of redirects and simplifies the checkout process for customers.
* Otherwise, initiate a transaction and redirect a customer to an external payment page hosted by the payment provider. 

#### What happens on the backend

Independantly of the storefront approach you chose, you must ensure that the app receives the transaction status to its `paymentUrl` and keeps the essential order details to complete the payment process while waiting.


---

# 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.ecwid.com/guides/payments/process-online-payment-requests/step-3.-initialize-the-transaction-from-payment-provider.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.