> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/xyb-platform-1/xyb-payments/payment-setup/payment-workflows/standard-payment-flow-tutorial.md).

# Standard Payment Flow - Tutorial

Learn how to configure and activate a **Standard Outbound Payment Flow,** a built-in workflow for handling the end-to-end lifecycle of outbound payments: from request, validation, and creation to authorization and clearance.

#### Step 1: Create a New Workflow

1. Go to **Workflows** > **Payments**
2. Click + **New Workflow**.

<div align="left"><figure><img src="https://2629557980-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft2bhF7867UQZjmdpxWXV%2Fuploads%2FJ71T8MX8p8YMCED580bZ%2Fimage.png?alt=media&amp;token=25e163ac-c96b-48de-a601-1f5a8711a53d" alt="" width="375"><figcaption></figcaption></figure></div>

3. In the **Plan** dropdown, select **Payment flow plan**. This is a pre-defined template that covers the full lifecycle of an outbound payment, handling validation, creation, authorization, and clearance steps automatically within the platform.
4. Give your workflow a name, e.g., Outbound EUR Payment
5. Choose a **workflow reference** (usually you can leave it as the default workflow-name unless you need to reference it programmatically)
6. Add a **description** to explain the purpose of the workflow.
7. Click **Create workflow.**

#### Step 2: Configure Workflow Parameters

The workflow canvas appears as you create the new workflow with pre-defined settings.&#x20;

This workflow defines the full lifecycle of an outbound payment—from the initial request and validation to creation, authorization, and final clearance. If validation fails, the payment is marked as invalid; if successful, it progresses through creation and authorization steps before reaching a cleared or failed state.

<figure><img src="https://2629557980-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft2bhF7867UQZjmdpxWXV%2Fuploads%2FtCHuZpipf5cv5wi58oKs%2Fimage.png?alt=media&amp;token=0f55d998-9ae3-4428-9d87-bd293996c9d0" alt=""><figcaption></figcaption></figure>

1. **Click Edit parameters** on top right. These parameters make the flow executable by telling it:

* Which schema to use (how to interpret the payment)
* How to move money across accounts (ledger movement instructions)

<div align="left" data-full-width="false"><figure><img src="https://2629557980-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ft2bhF7867UQZjmdpxWXV%2Fuploads%2FFDBvjXdCTz1wQjce9wMy%2Fimage.png?alt=media&amp;token=b1b5c92f-b191-400b-9df0-2d4f4a027c18" alt="" width="375"><figcaption></figcaption></figure></div>

&#x20;2\. Fill in the Schema Name and Ledger Instructions.

3. Click **Save parameters**.
4. Once reviewed, click **Activate** at the top right to make the workflow live.


---

# 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.xyb.co/xyb-platform-1/xyb-payments/payment-setup/payment-workflows/standard-payment-flow-tutorial.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.
