> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/journeys-and-pages/journey-steps/step-payment-information-as-a-separate-step.md).

# Collect Payment as a Separate Step

You can split account/contact collection and payment collection into two steps so customers don't re-enter information. The built-in **E-Commerce Checkout** journey does exactly this: a **Signup** step captures contact details (writing `firstName`, `lastName`, `email`, and `phone` to the journey context), and a separate **Billing** step collects the payment method.

Because the contact details are already in the journey context, the payment step's Zuora hosted page can be pre-filled with the name, email, phone, and address the customer already entered — they can still override them if billing differs.

To set this up in the journey builder (**Content → Journeys → Edit → Steps**):

1. Add a step for account/contact collection (e.g. a Signup page) and set its **Output variables** to the contact fields (`firstName`, `lastName`, `email`, `phone`).
2. Add a separate **Billing** step bound to a payment page, listing those same fields as **Input variables** so they pre-fill.

To keep payment on a single combined step instead, bind contact and payment collection to one page and skip the separate account step.


---

# 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.peakcommerce.com/product/journeys-and-pages/journey-steps/step-payment-information-as-a-separate-step.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.