> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stableyard.fi/llms.txt
> Use this file to discover all available pages before exploring further.
# Implementation guides
> Decide whether you are building a first-party or a third-party flow, then open the guide for it.
A first-party flow moves money between two ends that one legal entity owns. A third-party flow pays or collects for someone else, or runs accounts for your own customers, and the flow type decides the destination type, who must be verified and what Stableyard must enable.
## Answer these before you pick a guide
* **Funds owner.** Whose wallet funds each send, and whose account and destination receive. Stableyard never signs for a connected wallet: your customer does, or your platform if you provide the wallet.
* **Customer of record.** The [account](/universal-payment-account) Stableyard keeps for each party, and whether it is `individual` or `business`. `subjectType` is fixed at creation and decides which bank rails the account can ever reach.
* **Sender and beneficiary.** Who initiates and funds the movement, and who receives it. Either can differ from the customer of record.
* **Platform role.** Whether you move money only for your own business, or give each of your customers an account of their own.
* **Rails and markets.** Stablecoin only, or a bank on either end, and in which country. Stablecoin needs only your app's product access; fiat adds your organization's KYB and the verification of each account that uses it. See [Supported regions and currencies](/supported-regions-and-currencies).
* **Standing or one-off.** A standing facility, such as an on-ramp account, a deposit address or a linked bank, or one bounded payment with its own amount and expiry.
## First-party or third-party?
| Flow type | Route when | Example |
| - | - | - |
| **First-party** | One legal entity owns the account the money leaves or is collected into, and the destination it reaches | A customer's own US bank → their on-ramp account → their own wallet |
| **Third-party** | The beneficiary is a different legal entity, or you collect or move money on behalf of someone else | A customer's wallet → a supplier's bank account in Vietnam |
Still unsure? Ask whether the same legal entity owns both ends. If it does, the flow is first-party; if not, it is third-party.
## Route by what you already know
| You know that… | Guide | Pattern |
| - | - | - |
| An account holder funds their own account from their own US bank, repeatedly | [First-party flows](/guides/first-party-flows) | [Fund from your own bank](/guides/first-party-flows#pattern-fund-from-your-own-bank) |
| An account holder cashes out to a bank account they own | [First-party flows](/guides/first-party-flows) | [Withdraw to your own bank](/guides/first-party-flows#pattern-withdraw-to-your-own-bank) |
| An account holder sends their own stablecoin in, any amount, any time | [First-party flows](/guides/first-party-flows) | [Top up with stablecoin](/guides/first-party-flows#pattern-top-up-with-stablecoin) |
| You collect revenue for your own business and hold it in a wallet or Vault you control | [First-party flows](/guides/first-party-flows) | [Settle your own revenue](/guides/first-party-flows#pattern-settle-your-own-revenue) |
| You convert local-currency balances from processing merchant accounts you own | [First-party flows](/guides/first-party-flows) | [Acquirer or PSP, own merchant accounts](/guides/first-party-flows#pattern-acquirer-or-psp-own-merchant-accounts) |
| A sender pays someone else's bank account once, or a local merchant's QR code | [Third-party flows](/guides/third-party-flows) | [Pay local currency to someone else](/guides/third-party-flows#pattern-pay-local-currency-to-someone-else) |
| A sender pays a wallet, an account or a handle that belongs to someone else | [Third-party flows](/guides/third-party-flows) | [Pay in stablecoin](/guides/third-party-flows#pattern-pay-in-stablecoin) |
| Payers pay merchants whose accounts you keep | [Third-party flows](/guides/third-party-flows) | [Collect for a merchant](/guides/third-party-flows#pattern-collect-for-a-merchant) |
| You convert sub-merchant balances held in an intermediary settlement account | [Third-party flows](/guides/third-party-flows) | [Acquirer or PSP, sub-merchant balances](/guides/third-party-flows#pattern-acquirer-or-psp-sub-merchant-balances) |
| Your product gives each of its customers a Stableyard account | [Third-party flows](/guides/third-party-flows) | [Platform serves its customers](/guides/third-party-flows#pattern-platform-serves-its-customers) |
Published coverage describes what an agreement can include. What your credential can call today is narrower: build from `GET /v2/partners/config`, not from these guides. See [Get configuration](/api-reference/configuration/get-partner-config).
## Pick a guide
One legal entity owns both ends: fund from your own bank, withdraw to it, top up, and settle your own revenue.
Pay someone else's bank, merchant or wallet, collect for merchants, or run accounts for your customers.
## Go deeper by product
The guides say which pattern to build and in what order. The product tabs carry the full calls, fields and states.
Bring value into an account, and send it out to a wallet, an account or a bank.
Deliver verified value, net of fees, to the destination a receiving account chose.
Run accounts for your own customers, from your backend, inside your product.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.