Guides/Use Cases

Use Cases

The following use cases demonstrate common workflows that can be implemented using FV Merchant APIs. Each use case is designed to guide you through a complete, real-world flow rather than isolated API calls.

🔄 Common Outbound Payment Flow

All outbound transactions—whether bank payments or stablecoin transfers—follow a consistent pattern:

code


Create Beneficiary → Add Payment Instrument → Initiate Payment → Track Transaction

🧱 Core Concepts

1. Beneficiary A beneficiary represents the recipient of funds. This can be an individual or a business entity.

2. Payment Instrument A payment instrument defines how funds are delivered to the beneficiary. Examples include:

Bank accounts (ACH, Wire, SEPA)
Blockchain wallet addresses (USDC, PYUSD)

3. Payment A payment is created using a selected payment instrument to transfer funds to the beneficiary.

🔗 Relationship Between Entities

A single beneficiary can have multiple payment instruments
Each payment instrument must be unique and non-identical
Payment instruments can be of different types (e.g., ACH + Wire + Crypto wallet)

code


Beneficiary
   ├── Bank Account (ACH)
   ├── Bank Account (Wire)
   └── Crypto Wallet (USDC)

📌 How to Use These Use Cases

Each use case in this section builds on the flow above and demonstrates:

Required API calls
Example request/response payloads
How IDs flow between steps
Best practices for handling payments

Start with the use case most relevant to your integration (e.g., Send Bank Payments or Send Stablecoin Payments) and follow the steps sequentially.

These use cases are designed to help you integrate faster by focusing on end-to-end workflows rather than individual endpoints.