> ## Documentation Index
> Fetch the complete documentation index at: https://developer.tazapay.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Self-serve Requesting via API
> Create Collection Accounts — Virtual Accounts and Stablecoin Wallets — programmatically using the Tazapay API
Self-serve requesting via API is currently in **Beta**. Endpoints, fields, and webhook payloads may change while we stabilize the flow. For any issues, contact [support@tazapay.com](mailto:support@tazapay.com).
You can create Collection Accounts (Virtual Accounts and Stablecoin Wallets) for yourself or for your entities programmatically via the Tazapay API. Collection Accounts can only be created once you or your entity has been onboarded on Tazapay and approved by our team.
Before creating a collection account, call the [Metadata API](/api-reference/tazapay-api/virtual-account-metadata) to discover which account types, currencies, and payment method types are available for your account.
***
## High-level Flow
Ensure you or your entity has been onboarded on Tazapay and approved by our team before making API calls.
Call the [Collection Account Metadata API](/api-reference/tazapay-api/virtual-account-metadata) to discover:
* Available payment method types for your account
* Supported currencies and domicile countries
* Transfer limits and `on_behalf_of` restrictions
Call the [Collection Account Creation API](/api-reference/tazapay-api/create-collection-account) with your requirements — account type, country, currencies, and payment method type.
If Tazapay can fulfill the requirements, a Collection Account object is created with status `disabled` and an initial `enablement` request.
Subscribe to [webhook events](#webhook-events) to receive real-time status updates as the enablement request progresses. Once the request succeeds, the account status changes to `enabled` and is ready to receive funds.
***
## Collection Account Status Flow
Every Collection Account has a **status** — either `enabled` or `disabled` — that tells you whether it can currently receive funds.
This status is not set directly. Instead, it is determined by the state of **requests** associated with the account. Each time you want to enable, disable, or re-enable an account, a request is created and goes through its own lifecycle. The account status updates automatically based on how that request progresses.
There are three types of requests:
| Request Type | What it does |
| ----------------- | -------------------------------------------------------------------------------------------------------------- |
| **Enablement** | Activates the account so it can start receiving funds. Created automatically when the account is first set up. |
| **Disablement** | Deactivates the account so it stops accepting incoming payments. |
| **Re-enablement** | Reactivates a previously disabled account, if the account supports it. |
Each request moves through its own set of states — such as Processing, Requires Action, Approval Hold — before reaching a terminal state (Succeeded, Failed, or Cancelled). The account status at any point reflects the outcome of the most recent request.