> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/other-features/payment-orchestration/quickstart/payment-workflows.md).

# Supported Payment Workflows

Explore composable payment workflows for Vertical SaaS platforms

Juspay Hyperswitch's three-level profile architecture enables support for composable payment workflows, fulfilling the majority of use cases for a Vertical SaaS platform.

These workflows can be modularly organized to meet diverse business needs and provide flexibility based on client requirements. Here's a breakdown of key workflows:

### Possible Scenarios

**Direct Payments:** In the case of a client using a Vertical SaaS (VSaaS) platform, the client may prefer to authorize the customer's card only after the service is fulfilled. Therefore, the Vertical SaaS solution will need to verify and vault the card with the PSP, returning the PSP card token to the client.

**Customer Acquisition Payments:** For a client using a VSaaS platform, the primary goal is to acquire more customers. Thus, the client may rely on the platform to secure initial customer payments, while recurring payments are directly processed by the client through its PSP of choice.

**End-to-End Payments:** In cases where a client uses a Vertical SaaS platform to design new subscriptions and distribute them to customers, payments need to be more tightly integrated with the platform. As a result, the client may expect the platform to handle both customer acquisition and renewal payments through the PSP of choice on the client's behalf.

{% content-ref url="/pages/qti94giqukxy0Pmle32y" %}
[Export Payments Data To Redshift for Analytics](/integration-guide/account-management/analytics-and-operations/exporting-payments-data.md)
{% endcontent-ref %}


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/other-features/payment-orchestration/quickstart/payment-workflows.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.