Skip to content

docs(payment-types): simplify overview and add payment type selection guidance #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aimensahnoun wants to merge 1 commit into
base: 03-02-docs_api-features_migrate_crypto-to-fiat_page_to_legacy-aligned_content_replace_the_ai-generated_crypto-to-fiat_page_with_legacy_documentation_content_and_preserve_the_original_flow_wording_while_adapting_to_valid_mintlify_mdx_s
Choose a base branch
from
Open

docs(payment-types): simplify overview and add payment type selection guidance #60

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
58 changes: 26 additions & 32 deletions api-features/payment-types-overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,58 +1,52 @@
---
title: "Payment Types Overview"
description: "Understanding Invoice-first vs Payment-first workflows and direct payment types"
description: "Choose the right Request Network payment type for your integration"
---

<Warning>
**AI-Generated Content** – This page was generated with AI assistance and may contain inaccuracies. While likely close to accurate, please verify critical details with the [stable documentation](https://docs.request.network) or [contact support](https://github.com/orgs/RequestNetwork/discussions).
</Warning>

## Overview

Request Network supports two primary payment workflows and multiple payment types to accommodate different business needs.

## Payment Workflows

### Invoice-first Workflow
Create a payment request first, then allow customers to pay at their convenience.

**Use Cases:** Professional invoicing, B2B payments, formal payment collection

### Payment-first Workflow
Send payments directly without creating a request first.

**Use Cases:** Vendor payments, contractor payouts, immediate transfers
Request Network supports multiple payment types. This page helps you choose the right one for your integration.

## Direct Payment Types
## Payment Types

**Direct Payments** include Native, ERC20, and Conversion payments - the foundational payment methods that other features build upon.
Core payment types available in the API:

<CardGroup cols={3}>
<Card title="Native & ERC20" href="/api-features/standard-payments">
Simple crypto-to-crypto payments
Same-currency payments with native tokens and ERC20 tokens
</Card>

<Card title="Conversion" href="/api-features/conversion-payments">
Fiat-denominated, crypto-settled
Fiat-denominated requests paid in crypto
</Card>

<Card title="Crosschain" href="/api-features/crosschain-payments">
Multi-network payment routing
Pay from a different chain and token than the request currency
</Card>
</CardGroup>

## Used In

<CardGroup cols={2}>
<Card title="Invoicing" href="/use-cases/invoicing">
Invoice-first workflow with payment requests
<Card title="Batch Payments" href="/api-features/batch-payments">
Process multiple payments in one transaction
</Card>
<Card title="Payouts" href="/use-cases/payouts">
Payment-first workflow for direct transfers

<Card title="Recurring Payments" href="/api-features/recurring-payments">
Subscription-style scheduled payments
</Card>
</CardGroup>

## Implementation Details
## Choosing a Payment Type

<Steps>
<Step title="Choose your payment type">
Use Native/ERC20 for same-currency flows, Conversion for fiat pricing, and Crosschain when payer and request chains differ.
Comment on lines +41 to +42
Copy link

@greptile-apps greptile-apps bot Mar 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

consider breaking this into a bulleted list for easier scanning

Suggested change
<Step title="Choose your payment type">
Use Native/ERC20 for same-currency flows, Conversion for fiat pricing, and Crosschain when payer and request chains differ.
Choose based on your requirements:
- **Native/ERC20**: same-currency flows
- **Conversion**: fiat pricing with crypto settlement
- **Crosschain**: payer and request on different chains

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

</Step>

<Step title="Add advanced behavior if needed">
Use Batch for multi-recipient execution and Recurring for scheduled payments.
</Step>
</Steps>

## API Reference

See [API Reference - Payment Types](/api-reference/payment-types) for complete technical documentation.
For full endpoint schemas and examples, see [Request Network API Reference](https://api.request.network/open-api).