> 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.md).

# Payment Orchestration

Unified payment orchestration platform for managing multiple PSPs, payment methods, and optimizing payment lifecycle performance

Juspay Hyperswitch's Payment Orchestration platform is designed to simplify the complexities of managing multiple PSPs and various payment methods, ensuring optimal performance at every stage of the payment lifecycle.

Whether you're:

* **Accepting payments** from customers
* **Managing payouts** to vendors
* **Making recurring payments**

Hyperswitch provides a **unified solution** to maximize efficiency while minimizing costs.

Built for businesses of all sizes and types—**e-commerce platforms, SaaS companies, and marketplaces**—our orchestration platform ensures **reliability and flexibility**, helping you stay ahead in a competitive landscape.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;">Accept Payments</mark></td><td></td><td></td><td><a href="/other-features/payment-orchestration/quickstart.md">Accept Payments</a></td></tr><tr><td><mark style="color:blue;">Process Payouts</mark></td><td></td><td></td><td><a href="/other-features/connectors/payouts.md">Payouts Processors</a></td></tr><tr><td><mark style="color:blue;">Smart Routing</mark></td><td></td><td></td><td><a href="/other-features/payment-orchestration/smart-router.md">Smart Routing</a></td></tr><tr><td><mark style="color:blue;">Smart Retries</mark></td><td></td><td></td><td><a href="/integration-guide/workflows/smart-retries.md">Smart Retries</a></td></tr><tr><td><mark style="color:blue;">3DS / Strong Customer Authentication</mark></td><td></td><td></td><td><a href="/integration-guide/workflows/3ds-decision-manager.md">3DS / Strong Customer Authentication</a></td></tr><tr><td><mark style="color:blue;">Fraud &#x26; Risk Management</mark></td><td></td><td></td><td><a href="/integration-guide/workflows/fraud-and-risk-management.md">Fraud &amp; Risk Management</a></td></tr><tr><td><mark style="color:blue;">Subscriptions</mark></td><td></td><td></td><td><a href="/other-features/payment-orchestration/subscriptions.md">Subscriptions</a></td></tr></tbody></table>

{% hint style="info" %}
**Have Questions?**\
Join our [Slack Community](https://join.slack.com/t/hyperswitch-io/shared_invite/zt-2jqxmpsbm-WXUENx022HjNEy~Ark7Orw) to ask questions, share feedback, and collaborate.\
Prefer direct support? Use our [Contact Us](https://hyperswitch.io/contact-us) page to reach out.
{% endhint %}


---

# 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.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.