> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pesaswap.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Supported Payment Workflows
Pesaswap’s **three-level profile architecture** enables support for **composable payment workflows**, covering a wide range of scenarios commonly required by **Vertical SaaS platforms**.
These workflows are **modular** and **configurable**, allowing businesses to tailor payment handling based on specific operational needs and client expectations.
## Common Use Cases
### 1. **Direct Payments**
**Use Case:**
A client on a Vertical SaaS (VSaaS) platform may prefer to **authorize the customer’s card only after the service is delivered** (e.g., in service-based industries).
**Workflow:**
* The platform first **verifies and vaults** the card using the PSP (Payment Service Provider).
* A **PSP-issued card token** is returned to the client.
* The client can **authorize or charge** the card at a later point based on service fulfillment.
**Ideal For:**
* Postpaid services
* Reservation-based platforms
* On-demand service delivery
### 2. **Customer Acquisition Payments**
**Use Case:**
A VSaaS client may aim to **onboard new customers quickly**, with the platform handling **initial payments**, while recurring charges are managed independently by the client.
**Workflow:**
* The VSaaS platform processes the **first payment** for onboarding or subscription initiation.
* **Subsequent recurring payments** are directly handled by the client via their own PSP.
**Ideal For:**
* Freemium to paid transitions
* Trial-to-subscription workflows
* SaaS tools that delegate subscription billing later
### 3. **End-to-End Payments**
**Use Case:**
When a client uses a VSaaS platform to design, distribute, and manage subscriptions, they may want the **entire payment flow—both acquisition and renewals—to be handled by the platform**.
**Workflow:**
* The platform processes **initial and recurring payments**.
* The platform uses the client’s preferred PSP for all transactions.
* The client delegates **full payment lifecycle** to the platform.
**Ideal For:**
* Embedded fin
* Platforms offering white-label billing
* Clients seeking zero-touch payment infrastructure