From 19d9cbfc2cdf9650954822ee7a0f21bc271c1e8e Mon Sep 17 00:00:00 2001 From: MantisClone Date: Fri, 21 Nov 2025 16:10:40 -0500 Subject: [PATCH 01/12] docs: cleanup and improve Invoicing use case page - Remove AI-generated warning - Improve overview with benefits-focused copy - Fix quickstart steps (payment processing clarity) - Update demo section with correct EasyInvoice URL - Convert integration approaches from tabs to card layout - Add Info callout linking to integration comparison - Update Key API Features (8 features, proper links, reordered) - Improve What's Next section (3 focused cards) - Replace emojis with proper icons in title - Fix all em-dashes to normal dashes - Add missing features: Query Requests, Payment Types Overview - Update all other use case pages to use icons instead of emojis --- api-features/create-requests-query-status.mdx | 83 ------- use-cases/checkout.mdx | 3 +- use-cases/invoicing.mdx | 213 ++++++++++-------- use-cases/payment-detection.mdx | 3 +- use-cases/payouts.mdx | 3 +- use-cases/payroll.mdx | 3 +- use-cases/subscriptions.mdx | 3 +- 7 files changed, 125 insertions(+), 186 deletions(-) delete mode 100644 api-features/create-requests-query-status.mdx diff --git a/api-features/create-requests-query-status.mdx b/api-features/create-requests-query-status.mdx deleted file mode 100644 index 393239c..0000000 --- a/api-features/create-requests-query-status.mdx +++ /dev/null @@ -1,83 +0,0 @@ ---- -title: "Create Requests & Query Status" -description: "Request creation, management, and real-time status monitoring" ---- - -## Overview - -Request creation and status querying form the foundation of Request Network operations, enabling invoice generation and payment tracking throughout the lifecycle. - -## Request Creation - - - - Traditional invoicing workflows - - - - Direct payment collection - - - -## How It Works - -```mermaid -graph TD - A[Create Request] --> B[Generate ID] - B --> C[Store on IPFS] - C --> D[Index on Blockchain] - D --> E[Return Request] -``` - -**Process:** -1. **Create:** Submit request with payee, payer, and amount details -2. **Store:** Decentralized storage on IPFS -3. **Index:** Blockchain indexing for discovery -4. **Track:** Real-time status monitoring - -## Request Properties - -### Core Information -- **Payee:** Request creator/recipient -- **Payer:** Payment sender (optional) -- **Amount:** Payment amount and currency -- **Due Date:** Payment deadline - -### Payment Configuration -- **Payment Network:** ERC20, ETH, or custom -- **Accepted Tokens:** Supported payment currencies -- **Conversion:** Fiat-denominated crypto payments - -## Status Lifecycle - -### Request States -- `created` - Request initialized -- `pending` - Awaiting payment -- `paid` - Payment completed -- `cancelled` - Request cancelled - -### Payment States -- `no_payment` - No payment detected -- `partially_paid` - Partial payment received -- `paid` - Full payment completed -- `overpaid` - Payment exceeds requested amount - -## Query Methods - - - - Get specific request by ID - - - - Multiple requests in one call - - - -## Real-time Updates - -Combine with [Webhooks & Events](/api-features/webhooks-events) for instant status notifications. - -## Implementation Details - -See [API Reference - Requests](/api-reference/requests) for complete technical documentation. \ No newline at end of file diff --git a/use-cases/checkout.mdx b/use-cases/checkout.mdx index 88d4edc..6b4c24b 100644 --- a/use-cases/checkout.mdx +++ b/use-cases/checkout.mdx @@ -1,5 +1,6 @@ --- -title: "πŸ›’ Checkout" +title: "Checkout" +icon: "cart-shopping" description: "Add crypto payment checkout to your e-commerce platform with seamless customer experience" --- diff --git a/use-cases/invoicing.mdx b/use-cases/invoicing.mdx index 20d5659..a399be2 100644 --- a/use-cases/invoicing.mdx +++ b/use-cases/invoicing.mdx @@ -1,157 +1,174 @@ --- -title: "πŸ“„ Invoicing" +title: "Invoicing" +icon: "file-invoice" description: "Create crypto invoices with automatic payment detection and reconciliation" --- - -**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). - - ## Overview -Transform your invoicing workflow with Request Network. Create professional invoices, accept payments in 553+ currencies across 10 EVM chains, and maintain perfect payment records with zero reconciliation errors. +Bring instant, verifiable payments to your invoicing flow. Generate invoices in fiat or crypto, let customers pay in their preferred token across 9 EVM chains and 150+ currencies, and receive automatic reconciliation with on-chain payment detection - no manual tracking, no infrastructure overhead. -## πŸš€ Quickstart: Create Your First Invoice +**What you get:** +- **Permanent records** - Invoices stored on IPFS create a tamper-proof audit trail +- **Multi-currency flexibility** - Invoice in USD, get paid in crypto with automatic conversion +- **Instant reconciliation** - Every invoice automatically linked to its on-chain payment +- **Cross-chain support** - Accept payments across 9 networks in 150+ currencies +- **Webhook automation** - Real-time payment confirmations for backend integration - -**Get your first invoice paid in under 1 minute** - -*Interactive quickstart experience coming soon* - +## Quickstart - Generate a payment request with amount, recipient, and payment terms - - - Send the secure payment link to your customer + Call the [Create Request endpoint](/api-reference/request/create-request) with invoice details - - Customer pays with their preferred wallet and currency + + Use the returned payment call data to prompt the payer to sign and submit the transaction on-chain - Real-time payment detection and automatic reconciliation + Use [webhooks](/api-features/webhooks-events) for real-time payment notifications -## EasyInvoice Demo +## Invoicing Demo + +Try the complete invoicing workflow with EasyInvoice: + + + Create invoices, accept crypto payments, and track payment status - all powered by Request Network API + + +**What you'll see:** +- Invoice creation with Request Network +- Multiple payment currencies and chains +- Automatic payment detection +- Real-time status updates via webhooks + +## Integration Approaches -See the complete invoicing workflow in action with our demo application: + +Not sure which approach fits your needs? [See our detailed comparison of integration approaches β†’](/resources/integration-approaches) + - Complete invoicing workflow with Google login, dashboard metrics, and real-time updates + **Go live in minutes** + + Use our hosted application with no development required. + + - Dashboard analytics + - Multi-currency support + - Immediate deployment + + [Try it now β†’](https://easyinvoice.request.network) - Experience the full EasyInvoice application - - - -**Demo Features:** -- Google authentication and user management -- Professional invoice creation with custom branding -- Real-time payment tracking and notifications -- Dashboard with payment analytics and metrics -- Multi-currency support (USD invoicing, crypto settlement) - -## Integration Options - -Choose the approach that best fits your needs: - - - - **Best for:** Quick deployment, immediate invoicing capabilities + **Customize for your brand** - Deploy EasyInvoice directly for your business: - - Ready-to-use invoicing interface - - No development required - - Hosted solution with custom domain support + Clone and modify the open-source application to match your needs. - [Deploy EasyInvoice β†’](#) - - - - **Best for:** Custom branding, workflow modifications + - Full source code access + - Custom branding + - Add your own features - Customize EasyInvoice for your specific needs: - - Clone the repository - - Modify UI/UX to match your brand - - Add custom business logic - - Requires API key setup + [Forking guide β†’](#) + + + + + **Complete control** - [Fork Repository β†’](#) | [Setup Guide β†’](#) - - - - **Best for:** White-label solutions, full control + Build a custom solution integrated with your existing systems. - Build your own invoicing system using Request Network API: - - Complete customization freedom - - Integrate with existing systems - - Pure API integration + - White-label ready + - Full customization + - Add fee layers + - Non-custodial architecture - [API Documentation β†’](/api-features/payment-types) - - + [API docs β†’](/api-features/create-requests) + ## Key API Features for Invoicing - Generate payment requests with flexible parameters and metadata + Generate payment requests with amount, recipient, and payment terms - Invoice in USD, get paid in crypto with automatic conversion + Fiat-denominated invoices settled in crypto with real-time price conversion + + + + Pay multiple invoices in a single transaction + + + + Accept payments across 9 different blockchain networks - Set up subscription billing and automated recurring invoices + Automate recurring invoice generation for ongoing vendor relationships - Real-time payment notifications for instant reconciliation + Automatic detection and verification of payments across chains - Accept installment payments and partial settlements + Build invoicing dashboards with historical invoice data and status tracking - Add invoice numbers, tax info, and business data + Explore all available payment methods and configurations @@ -159,7 +176,7 @@ Choose the approach that best fits your needs: @@ -167,18 +184,18 @@ Choose the approach that best fits your needs: - Learn about payment types and advanced capabilities + See code examples for common invoicing workflows - Review supported chains and currencies + See which networks and tokens you can use diff --git a/use-cases/payment-detection.mdx b/use-cases/payment-detection.mdx index b51f94b..04d7c84 100644 --- a/use-cases/payment-detection.mdx +++ b/use-cases/payment-detection.mdx @@ -1,5 +1,6 @@ --- -title: "πŸ’³ Payment Detection" +title: "Payment Detection" +icon: "credit-card" description: "Automatically detect and verify crypto payments with real-time blockchain monitoring and webhooks" --- diff --git a/use-cases/payouts.mdx b/use-cases/payouts.mdx index 9f518b9..bb8a084 100644 --- a/use-cases/payouts.mdx +++ b/use-cases/payouts.mdx @@ -1,5 +1,6 @@ --- -title: "πŸ’° Payouts" +title: "Payouts" +icon: "money-bill-transfer" description: "Send batch payments to multiple recipients with automatic tracking and reconciliation" --- diff --git a/use-cases/payroll.mdx b/use-cases/payroll.mdx index 2adff37..d1aefe5 100644 --- a/use-cases/payroll.mdx +++ b/use-cases/payroll.mdx @@ -1,5 +1,6 @@ --- -title: "πŸ’Ό Payroll" +title: "Payroll" +icon: "briefcase" description: "Pay your team in crypto with automated payroll runs and compliance tracking" --- diff --git a/use-cases/subscriptions.mdx b/use-cases/subscriptions.mdx index 35e3f3e..0607483 100644 --- a/use-cases/subscriptions.mdx +++ b/use-cases/subscriptions.mdx @@ -1,5 +1,6 @@ --- -title: "πŸ”„ Subscriptions" +title: "Subscriptions" +icon: "rotate" description: "Implement recurring crypto payments for subscription-based business models" --- From cccee43beb4609222b714c22700a731047e694d9 Mon Sep 17 00:00:00 2001 From: MantisClone Date: Fri, 21 Nov 2025 16:31:36 -0500 Subject: [PATCH 02/12] refine: simplify Quickstart Step 2 wording for clarity --- use-cases/invoicing.mdx | 18 +----------------- 1 file changed, 1 insertion(+), 17 deletions(-) diff --git a/use-cases/invoicing.mdx b/use-cases/invoicing.mdx index a399be2..bbc9345 100644 --- a/use-cases/invoicing.mdx +++ b/use-cases/invoicing.mdx @@ -22,7 +22,7 @@ Bring instant, verifiable payments to your invoicing flow. Generate invoices in Call the [Create Request endpoint](/api-reference/request/create-request) with invoice details - Use the returned payment call data to prompt the payer to sign and submit the transaction on-chain + Use the payment data to show payment options, then guide the payer through wallet signature and submission Use [webhooks](/api-features/webhooks-events) for real-time payment notifications @@ -131,14 +131,6 @@ Not sure which approach fits your needs? [See our detailed comparison of integra Pay multiple invoices in a single transaction - - Accept payments across 9 different blockchain networks - - Build invoicing dashboards with historical invoice data and status tracking - - - Explore all available payment methods and configurations - ## What's Next? From 4d6af66002df02f06df63f69d633be5fecbb8154 Mon Sep 17 00:00:00 2001 From: MantisClone Date: Fri, 21 Nov 2025 16:35:41 -0500 Subject: [PATCH 03/12] enhance: add tooltips for technical terms and Check callout after demo --- use-cases/invoicing.mdx | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/use-cases/invoicing.mdx b/use-cases/invoicing.mdx index bbc9345..c6f0508 100644 --- a/use-cases/invoicing.mdx +++ b/use-cases/invoicing.mdx @@ -9,9 +9,9 @@ description: "Create crypto invoices with automatic payment detection and reconc Bring instant, verifiable payments to your invoicing flow. Generate invoices in fiat or crypto, let customers pay in their preferred token across 9 EVM chains and 150+ currencies, and receive automatic reconciliation with on-chain payment detection - no manual tracking, no infrastructure overhead. **What you get:** -- **Permanent records** - Invoices stored on IPFS create a tamper-proof audit trail +- **Permanent records** - Invoices stored on IPFS create a tamper-proof audit trail - **Multi-currency flexibility** - Invoice in USD, get paid in crypto with automatic conversion -- **Instant reconciliation** - Every invoice automatically linked to its on-chain payment +- **Instant reconciliation** - Every invoice automatically linked to its on-chain payment - **Cross-chain support** - Accept payments across 9 networks in 150+ currencies - **Webhook automation** - Real-time payment confirmations for backend integration @@ -47,6 +47,10 @@ Try the complete invoicing workflow with EasyInvoice: - Automatic payment detection - Real-time status updates via webhooks + +**Ready to integrate?** If EasyInvoice meets your needs, you can start using it immediately. For custom requirements, explore the integration options below. + + ## Integration Approaches @@ -99,7 +103,7 @@ Not sure which approach fits your needs? [See our detailed comparison of integra - White-label ready - Full customization - Add fee layers - - Non-custodial architecture + - Non-custodial architecture [API docs β†’](/api-features/create-requests) From 557868d2f6303f045070d453d7064e41d4b49a41 Mon Sep 17 00:00:00 2001 From: MantisClone Date: Fri, 21 Nov 2025 18:38:21 -0500 Subject: [PATCH 04/12] fix: address CodeRabbit review comments - indentation and links --- use-cases/invoicing.mdx | 36 ++++++++++++++++++------------------ 1 file changed, 18 insertions(+), 18 deletions(-) diff --git a/use-cases/invoicing.mdx b/use-cases/invoicing.mdx index c6f0508..467a0d2 100644 --- a/use-cases/invoicing.mdx +++ b/use-cases/invoicing.mdx @@ -19,7 +19,7 @@ Bring instant, verifiable payments to your invoicing flow. Generate invoices in - Call the [Create Request endpoint](/api-reference/request/create-request) with invoice details + Call the [Create Request endpoint](/api-features/create-requests) with invoice details Use the payment data to show payment options, then guide the payer through wallet signature and submission @@ -91,22 +91,22 @@ Not sure which approach fits your needs? [See our detailed comparison of integra - - **Complete control** - - Build a custom solution integrated with your existing systems. - - - White-label ready - - Full customization - - Add fee layers - - Non-custodial architecture - - [API docs β†’](/api-features/create-requests) - + + **Complete control** + + Build a custom solution integrated with your existing systems. + + - White-label ready + - Full customization + - Add fee layers + - Non-custodial architecture + + [API docs β†’](/api-features/create-requests) + ## Key API Features for Invoicing @@ -137,7 +137,7 @@ Not sure which approach fits your needs? [See our detailed comparison of integra Automate recurring invoice generation for ongoing vendor relationships From b682c614af93b63cb416ad1704ea0ef83a13e5ad Mon Sep 17 00:00:00 2001 From: MantisClone Date: Fri, 21 Nov 2025 21:33:21 -0500 Subject: [PATCH 05/12] Clean up Payment Detection use case page (Issue #29) - Remove AI-generated content warning - Update chain count from '10+ EVM chains' to accurate '9 EVM chains' - Update currency count to '150+ currencies' for consistency - Rewrite Overview to lead with problem/solution (crypto payments lack context) - Add tooltips for technical terms (transaction hash, blockchain, webhook, confirmations) - Update 'When to Use' cards with accurate counts and clearer copy - Refine 'Common Scenarios' with minor improvements and tooltip - Add Info callout linking to technical details (replaces deleted section) - Update 'How Payment Detection Works' steps with tooltips - Add Info callout explaining Payment Detection powers all use cases - Remove 'Detection Features' section (technical details belong in API feature page) - Remove 'Detection-Only vs Full Workflows' Tabs (confusing framing) - Remove 'Implementation Example' code section (belongs in API Reference) - Remove 'Supported Networks & Currencies' section (have dedicated page) - Rename 'API Integration' to 'Key API Features for Payment Detection' - Reorder and update API feature cards for clarity - Update 'Next Steps' to 'What's Next?' with 3 focused cards - Link to welcome page demo showing payment collision prevention - Reduce page from ~310 lines to ~180 lines (42% reduction) Follows template from Invoicing page cleanup (PR #26) References Issue #29 and parent Issue #18 --- use-cases/payment-detection.mdx | 280 +++++++++----------------------- 1 file changed, 77 insertions(+), 203 deletions(-) diff --git a/use-cases/payment-detection.mdx b/use-cases/payment-detection.mdx index 04d7c84..edc753f 100644 --- a/use-cases/payment-detection.mdx +++ b/use-cases/payment-detection.mdx @@ -4,31 +4,37 @@ icon: "credit-card" description: "Automatically detect and verify crypto payments with real-time blockchain monitoring and webhooks" --- - -**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). - - ## Overview -Payment Detection monitors blockchain networks to automatically identify and verify when payments are completed. Add crypto payment acceptance to your existing systems without rebuilding your entire infrastructure. +Traditional crypto payments lack business context. You receive a transaction hash, but don't know which customer, invoice, or order it's for. Manual reconciliation is error-prone and doesn't scale. + +Request IDs solve this by attaching business context directly to payments. Every payment includes a unique Request ID, enabling automatic attribution and reconciliation with cryptographic certainty. + +**What you get:** +- **Automatic attribution** - Every payment linked to its request (invoice, order, subscription) +- **Multi-chain monitoring** - Track payments across 9 EVM chains in 150+ currencies +- **Real-time notifications** - Webhooks for instant payment confirmations +- **Zero manual work** - No spreadsheets, no guessing, no payment collisions + +[See how Request IDs prevent payment collisions (welcome page demo) β†’](/use-cases/welcome) ## When to Use Payment Detection - - You already have invoicing, billing, or business systems and just need crypto payment acceptance + + You have invoicing, billing, or business systems and need to add crypto payment acceptance - Collect payments at scale to one wallet address and automatically attribute each payment + Collect thousands of payments to one wallet and automatically attribute each one - Need instant payment confirmation without manual blockchain checking + Get instant payment confirmation without manual blockchain monitoring - Accept payments across Ethereum, Polygon, BSC, and 10+ EVM chains + Accept payments across 9 EVM chains in 150+ currencies @@ -40,21 +46,23 @@ Accept crypto donations to a single wallet and automatically attribute each to t **Example:** A nonprofit collects donations from hundreds of donors to one Ethereum address. Each donation includes a Request ID, enabling automatic attribution and thank-you emails. ### SaaS Adding Crypto Payments -Existing subscription or billing platform adds crypto as a payment option alongside credit cards. +Add crypto as a payment option to existing subscription or billing platforms alongside credit cards. **Example:** A SaaS company uses Stripe for card payments but wants to offer USDC payments. Payment Detection monitors for crypto payments and updates subscription status automatically. -### Manual Invoices + Crypto Detection +### Manual Invoices with Crypto Settlement Send invoices through existing channels (email, PDF) and let customers pay in crypto with automatic detection. -**Example:** A freelancer emails invoices as PDFs with a Request ID. Clients pay in crypto, and the freelancer's accounting software automatically marks invoices as paid via webhook. +**Example:** A freelancer emails invoices as PDFs with a Request ID. Clients pay in crypto, and the freelancer's accounting software automatically marks invoices as paid via webhook. ### High-Volume Payment Collection -Collect thousands of payments without creating new wallet addresses for each transaction. +Collect thousands of payments without generating unique wallet addresses for each transaction. -**Example:** An e-commerce platform processes 10,000+ crypto orders per day. Instead of generating unique addresses, each order gets a Request ID for attribution. +**Example:** An e-commerce platform processes 10,000+ crypto orders per day. Instead of unique addresses, each order gets a Request ID for attribution. ---- + +These scenarios all use automatic payment detection. [See technical details on detection methods and configuration β†’](/api-features/payment-detection) + ## How Payment Detection Works @@ -64,220 +72,86 @@ Collect thousands of payments without creating new wallet addresses for each tra - Request Network continuously scans supported blockchains for transactions matching your requests + Request Network continuously scans supported blockchains for transactions matching your requests - - When a matching payment is found, Request Network verifies amount, currency, and confirmations + + When a matching payment is found, Request Network verifies amount, currency, and confirmations - Your system receives a real-time webhook with payment details and status + Your system receives a real-time webhook with payment details and status - Your business logic updates invoice status, triggers fulfillment, or sends receipts + Your business logic updates invoice status, triggers fulfillment, or sends receipts - no manual work needed ---- + +Payment Detection powers all Request Network use cases: [invoicing](/use-cases/invoicing), [payouts](/use-cases/payouts), [payroll](/use-cases/payroll), [checkout](/use-cases/checkout), and [subscriptions](/use-cases/subscriptions). Every use case includes automatic detection with no manual tracking. + -## Detection Features - -### Real-time Blockchain Scanning -- **Multi-chain monitoring:** Ethereum, Polygon, Arbitrum, Optimism, BSC, Gnosis, Fantom, Avalanche, and more -- **Sub-minute detection:** Typically detect payments within seconds of blockchain confirmation -- **Confirmation tracking:** Configurable confirmation thresholds for different security requirements - -### Payment Verification -- **Amount matching:** Verify exact payment amount or accept partial payments -- **Currency validation:** Support for 553+ tokens across all supported chains -- **Smart contract verification:** Detect payments through ERC20, native tokens, and conversion proxies - -### Webhook Integration -- **Event notifications:** `payment.detected`, `payment.confirmed`, `payment.failed` -- **Retry logic:** Automatic webhook retries with exponential backoff -- **Signature verification:** Cryptographically signed webhooks for security - ---- - -## API Integration +## Key API Features for Payment Detection - - Real-time payment notifications sent to your server + + Monitor blockchain transactions and match payments to requests automatically - - Poll for payment status on demand + + Real-time notifications when payments are detected, confirmed, or failed - - Technical details on detection methods and configuration + + Check request status and payment history on demand - - Check request status including payment state + + Retrieve detailed payment information including confirmations and amounts ---- - -## Detection-Only vs Full Workflows - -Understanding when to use standalone payment detection versus integrated workflows: - - - - **Best for:** Existing systems that just need crypto payment acceptance - - **What you handle:** - - Create invoices/requests in your existing system - - Generate Request IDs via API - - Include Request ID in payment instructions - - Receive webhooks when payments are detected - - Update your system based on payment status - - **What Request Network handles:** - - Blockchain monitoring across all chains - - Payment verification and confirmation tracking - - Webhook delivery with retry logic - - Permanent on-chain payment records - - **Example:** QuickBooks + crypto payments via Request Network detection - - - - **Best for:** Building new invoicing systems from scratch - - **What Request Network handles:** - - Invoice creation with structured data - - Payment link generation - - Payment processing - - Payment detection - - Complete payment lifecycle management - - **What you handle:** - - User interface and experience - - Customer management - - Business logic and workflows - - **Example:** [EasyInvoice](/use-cases/invoicing) - full-stack invoicing application - - [Learn more β†’](/use-cases/invoicing) - - - - **Payment detection powers all Request Network use cases:** - - - **[Payouts](/use-cases/payouts):** Detection confirms batch payment completion - - **[Payroll](/use-cases/payroll):** Detection verifies salary payments - - **[Checkout](/use-cases/checkout):** Detection triggers order fulfillment - - **[Subscriptions](/use-cases/subscriptions):** Detection handles recurring payments - - Each use case combines request creation with payment detection for specific workflows. - - - ---- - -## Implementation Example +## What's Next? -Here's a minimal example of using payment detection with webhooks: - - -```javascript Node.js - Create Request -const response = await fetch('https://api.request.network/requests', { - method: 'POST', - headers: { - 'Authorization': `Bearer ${API_KEY}`, - 'Content-Type': 'application/json' - }, - body: JSON.stringify({ - currency: 'USDC-matic', - expectedAmount: '100.00', - paymentAddress: '0x...your-wallet', - reason: 'Invoice #12345' - }) -}); - -const { requestId } = await response.json(); -// Include requestId in payment instructions to customer -``` - -```javascript Node.js - Webhook Handler -app.post('/webhooks/request', (req, res) => { - const { eventType, requestId, paymentAmount, status } = req.body; - - if (eventType === 'payment.detected') { - // Payment detected on blockchain - console.log(`Payment detected for ${requestId}: ${paymentAmount}`); - - // Update your system - await updateInvoiceStatus(requestId, 'PAID'); - await sendReceiptEmail(requestId); - } - - res.status(200).send('OK'); -}); -``` - -```python Python - Webhook Handler -from flask import Flask, request - -@app.route('/webhooks/request', methods=['POST']) -def handle_webhook(): - data = request.json - - if data['eventType'] == 'payment.detected': - request_id = data['requestId'] - payment_amount = data['paymentAmount'] - - # Update your system - update_invoice_status(request_id, 'PAID') - send_receipt_email(request_id) - - return '', 200 -``` - - ---- - -## Supported Networks & Currencies - -### Mainnet Networks -- **Ethereum:** ETH, USDC, USDT, DAI, and 200+ ERC20 tokens -- **Polygon:** MATIC, USDC, USDT, DAI, and 150+ tokens -- **Arbitrum, Optimism, BSC, Gnosis, Fantom, Avalanche:** Full ERC20 support - -### Detection Speed -- **Ethereum:** ~15 seconds per confirmation -- **Polygon:** ~2 seconds per confirmation -- **Layer 2s:** Sub-second to ~2 seconds - -### Testnet Support -Available on Sepolia, Mumbai, and other testnets for development - -[View all supported chains and currencies β†’](/resources/supported-chains-and-currencies) - ---- - -## Next Steps - - - - Set up authentication and create your first request - - - - Set up real-time payment notifications + + + Set up your account and get API credentials - - Learn how to check payment status programmatically + + Technical deep dive on detection methods and configuration - - Manage API keys and monitor requests in real-time + + See which networks and tokens you can use From d511757cc87959d2c502a1008f3370df104c9d87 Mon Sep 17 00:00:00 2001 From: MantisClone Date: Fri, 21 Nov 2025 23:12:28 -0500 Subject: [PATCH 06/12] Simplify 'How Payment Detection Works' section - Reduce from 5 steps to 4 steps focused on user journey - Remove technical implementation details (verification, confirmations, reconciliation logic) - Make steps more actionable and less technical - Update Info callout to explicitly link to technical details in API Features page - Leave complex explanations for dedicated API Features page --- use-cases/payment-detection.mdx | 22 +++++++++------------- 1 file changed, 9 insertions(+), 13 deletions(-) diff --git a/use-cases/payment-detection.mdx b/use-cases/payment-detection.mdx index edc753f..68f3341 100644 --- a/use-cases/payment-detection.mdx +++ b/use-cases/payment-detection.mdx @@ -67,29 +67,25 @@ These scenarios all use automatic payment detection. [See technical details on d ## How Payment Detection Works - - Customer sends crypto payment including the Request ID in the transaction reference + + Generate a unique Request ID when creating an invoice, order, or payment request - - Request Network continuously scans supported blockchains for transactions matching your requests + + Customer sends payment to your wallet address - the Request ID is included in the transaction - - When a matching payment is found, Request Network verifies amount, currency, and confirmations + + Request Network monitors the blockchain and matches the payment to your request - - Your system receives a real-time webhook with payment details and status - - - - Your business logic updates invoice status, triggers fulfillment, or sends receipts - no manual work needed + + Your system receives a webhook confirming the payment -Payment Detection powers all Request Network use cases: [invoicing](/use-cases/invoicing), [payouts](/use-cases/payouts), [payroll](/use-cases/payroll), [checkout](/use-cases/checkout), and [subscriptions](/use-cases/subscriptions). Every use case includes automatic detection with no manual tracking. +Payment Detection powers all Request Network use cases: [invoicing](/use-cases/invoicing), [payouts](/use-cases/payouts), [payroll](/use-cases/payroll), [checkout](/use-cases/checkout), and [subscriptions](/use-cases/subscriptions). [See technical details on detection methods, confirmation thresholds, and implementation β†’](/api-features/payment-detection) ## Key API Features for Payment Detection From c24254fb0ac5c1959d08847aadd733778adb9a7c Mon Sep 17 00:00:00 2001 From: MantisClone Date: Sat, 22 Nov 2025 07:54:09 -0500 Subject: [PATCH 07/12] Fix technical accuracy: use payment reference instead of Request ID - Update Overview to explain reference-based payment detection - Clarify that 16-character payment reference is included in transactions, not Request ID - Update 'How Payment Detection Works' steps to reflect actual technical flow - Update all examples to use 'payment reference' terminology consistently - Maintain simplified language while being technically accurate Based on official docs: https://docs.request.network/request-network-api/payment-detection.md --- use-cases/payment-detection.mdx | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/use-cases/payment-detection.mdx b/use-cases/payment-detection.mdx index 68f3341..aa69265 100644 --- a/use-cases/payment-detection.mdx +++ b/use-cases/payment-detection.mdx @@ -8,15 +8,15 @@ description: "Automatically detect and verify crypto payments with real-time blo Traditional crypto payments lack business context. You receive a transaction hash, but don't know which customer, invoice, or order it's for. Manual reconciliation is error-prone and doesn't scale. -Request IDs solve this by attaching business context directly to payments. Every payment includes a unique Request ID, enabling automatic attribution and reconciliation with cryptographic certainty. +Request Network solves this with reference-based payment detection. Each request automatically generates a unique payment referenceβ€”a 16-character identifier included in the blockchain transaction. This connects every payment back to your specific invoice, order, or subscription with cryptographic certainty. **What you get:** -- **Automatic attribution** - Every payment linked to its request (invoice, order, subscription) +- **Automatic attribution** - Every payment linked to its request via payment reference - **Multi-chain monitoring** - Track payments across 9 EVM chains in 150+ currencies - **Real-time notifications** - Webhooks for instant payment confirmations - **Zero manual work** - No spreadsheets, no guessing, no payment collisions -[See how Request IDs prevent payment collisions (welcome page demo) β†’](/use-cases/welcome) +[See how payment references prevent payment collisions (welcome page demo) β†’](/use-cases/welcome) ## When to Use Payment Detection @@ -43,7 +43,7 @@ Request IDs solve this by attaching business context directly to payments. Every ### Donations with Attribution Accept crypto donations to a single wallet and automatically attribute each to the correct donor, campaign, or cause. -**Example:** A nonprofit collects donations from hundreds of donors to one Ethereum address. Each donation includes a Request ID, enabling automatic attribution and thank-you emails. +**Example:** A nonprofit collects donations from hundreds of donors to one Ethereum address. Each donation includes a unique payment reference, enabling automatic attribution and thank-you emails. ### SaaS Adding Crypto Payments Add crypto as a payment option to existing subscription or billing platforms alongside credit cards. @@ -53,12 +53,12 @@ Add crypto as a payment option to existing subscription or billing platforms alo ### Manual Invoices with Crypto Settlement Send invoices through existing channels (email, PDF) and let customers pay in crypto with automatic detection. -**Example:** A freelancer emails invoices as PDFs with a Request ID. Clients pay in crypto, and the freelancer's accounting software automatically marks invoices as paid via webhook. +**Example:** A freelancer emails invoices as PDFs with a payment reference. Clients include the reference when paying in crypto, and the freelancer's accounting software automatically marks invoices as paid via webhook. ### High-Volume Payment Collection Collect thousands of payments without generating unique wallet addresses for each transaction. -**Example:** An e-commerce platform processes 10,000+ crypto orders per day. Instead of unique addresses, each order gets a Request ID for attribution. +**Example:** An e-commerce platform processes 10,000+ crypto orders per day. Instead of unique addresses, each order gets a unique payment reference for attribution. These scenarios all use automatic payment detection. [See technical details on detection methods and configuration β†’](/api-features/payment-detection) @@ -67,20 +67,20 @@ These scenarios all use automatic payment detection. [See technical details on d ## How Payment Detection Works - - Generate a unique Request ID when creating an invoice, order, or payment request + + When you create a request, a unique 16-character payment reference is automatically generated - Customer sends payment to your wallet address - the Request ID is included in the transaction + Customer sends payment to your wallet address including the payment reference in the transaction - Request Network monitors the blockchain and matches the payment to your request + Request Network monitors blockchains for transactions containing your payment references - Your system receives a webhook confirming the payment + When a match is found, your request status updates and you receive a webhook notification From 5bb792db167f14751bc8083e48e8c57edbeff4fc Mon Sep 17 00:00:00 2001 From: MantisClone Date: Sat, 22 Nov 2025 08:13:44 -0500 Subject: [PATCH 08/12] Use Request ID terminology throughout Use Case page (Option A) Strategy: Use Case page uses user-facing 'Request ID' abstraction, API Features page will explain 'Payment Reference' implementation details. Changes: - Overview: Request IDs attach business context (not payment references) - Steps: Request ID is automatically embedded (abstracts payment reference mechanism) - Examples: All use 'Request ID' consistently - Maintains consistency with Welcome page vocabulary - Links to API Features page for technical deep dive Terminology strategy: - Request ID = user-facing identifier users interact with - Payment Reference = 16-char derived identifier for smart contracts - API Features page will explain the derivation and correlation - Use Case page focuses on what/why, not how This maintains technical accuracy while providing appropriate abstraction level for use case documentation. --- use-cases/payment-detection.mdx | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/use-cases/payment-detection.mdx b/use-cases/payment-detection.mdx index aa69265..989d5f5 100644 --- a/use-cases/payment-detection.mdx +++ b/use-cases/payment-detection.mdx @@ -8,15 +8,15 @@ description: "Automatically detect and verify crypto payments with real-time blo Traditional crypto payments lack business context. You receive a transaction hash, but don't know which customer, invoice, or order it's for. Manual reconciliation is error-prone and doesn't scale. -Request Network solves this with reference-based payment detection. Each request automatically generates a unique payment referenceβ€”a 16-character identifier included in the blockchain transaction. This connects every payment back to your specific invoice, order, or subscription with cryptographic certainty. +Request IDs solve this by attaching business context to every payment. Each request gets a unique Request ID that connects payments back to your specific invoice, order, or subscription with cryptographic certainty. **What you get:** -- **Automatic attribution** - Every payment linked to its request via payment reference +- **Automatic attribution** - Every payment linked to its request via Request ID - **Multi-chain monitoring** - Track payments across 9 EVM chains in 150+ currencies - **Real-time notifications** - Webhooks for instant payment confirmations - **Zero manual work** - No spreadsheets, no guessing, no payment collisions -[See how payment references prevent payment collisions (welcome page demo) β†’](/use-cases/welcome) +[See how Request IDs prevent payment collisions (welcome page demo) β†’](/use-cases/welcome) ## When to Use Payment Detection @@ -43,7 +43,7 @@ Request Network solves this with reference-based payment detection. Each request ### Donations with Attribution Accept crypto donations to a single wallet and automatically attribute each to the correct donor, campaign, or cause. -**Example:** A nonprofit collects donations from hundreds of donors to one Ethereum address. Each donation includes a unique payment reference, enabling automatic attribution and thank-you emails. +**Example:** A nonprofit collects donations from hundreds of donors to one Ethereum address. Each donation is linked to a unique Request ID, enabling automatic attribution and thank-you emails. ### SaaS Adding Crypto Payments Add crypto as a payment option to existing subscription or billing platforms alongside credit cards. @@ -53,12 +53,12 @@ Add crypto as a payment option to existing subscription or billing platforms alo ### Manual Invoices with Crypto Settlement Send invoices through existing channels (email, PDF) and let customers pay in crypto with automatic detection. -**Example:** A freelancer emails invoices as PDFs with a payment reference. Clients include the reference when paying in crypto, and the freelancer's accounting software automatically marks invoices as paid via webhook. +**Example:** A freelancer emails invoices as PDFs with a Request ID. When clients pay in crypto, the freelancer's accounting software automatically marks invoices as paid via webhook. ### High-Volume Payment Collection Collect thousands of payments without generating unique wallet addresses for each transaction. -**Example:** An e-commerce platform processes 10,000+ crypto orders per day. Instead of unique addresses, each order gets a unique payment reference for attribution. +**Example:** An e-commerce platform processes 10,000+ crypto orders per day. Instead of unique addresses, each order gets a unique Request ID for attribution. These scenarios all use automatic payment detection. [See technical details on detection methods and configuration β†’](/api-features/payment-detection) @@ -67,20 +67,20 @@ These scenarios all use automatic payment detection. [See technical details on d ## How Payment Detection Works - - When you create a request, a unique 16-character payment reference is automatically generated + + When you create a request, it gets a unique Request ID for tracking - Customer sends payment to your wallet address including the payment reference in the transaction + Customer sends payment to your wallet address - the Request ID is automatically embedded - Request Network monitors blockchains for transactions containing your payment references + Request Network monitors blockchains and matches payments to your requests - When a match is found, your request status updates and you receive a webhook notification + When a payment is matched, your request status updates and you receive a webhook notification From 1fa625d6b4b0e133d33176bcc865f87ec8035a73 Mon Sep 17 00:00:00 2001 From: MantisClone Date: Sat, 22 Nov 2025 08:31:39 -0500 Subject: [PATCH 09/12] Improve terminology precision in How It Works section - Replace 'embedded' with 'included in the transaction' (more precise, commonly used term) - Change 'request status updates and you receive webhook' to 'you receive webhook with payment details' - Avoids claiming request state changes (technically inaccurate - IPFS stores request state, payments detected via subgraphs, status derived from combining both) - Focuses on what user experiences (webhook notification) rather than internal state management --- use-cases/payment-detection.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/use-cases/payment-detection.mdx b/use-cases/payment-detection.mdx index 989d5f5..0868e69 100644 --- a/use-cases/payment-detection.mdx +++ b/use-cases/payment-detection.mdx @@ -72,7 +72,7 @@ These scenarios all use automatic payment detection. [See technical details on d - Customer sends payment to your wallet address - the Request ID is automatically embedded + Customer sends payment to your wallet address - the Request ID is automatically included in the transaction @@ -80,7 +80,7 @@ These scenarios all use automatic payment detection. [See technical details on d - When a payment is matched, your request status updates and you receive a webhook notification + When a payment is detected, you receive a webhook notification with payment details From aaa5b545b1a9273e400ca7b91f2b59e2b6e3d6d9 Mon Sep 17 00:00:00 2001 From: MantisClone Date: Sat, 22 Nov 2025 08:35:15 -0500 Subject: [PATCH 10/12] Refine terminology: 'connected' instead of 'included' - Change 'included in the transaction' to 'connected to the transaction' - Fix tooltip formatting: move comma inside tooltip for 'transaction hash' - 'Connected' is more accurate and user-friendly than 'included' --- use-cases/payment-detection.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/use-cases/payment-detection.mdx b/use-cases/payment-detection.mdx index 0868e69..46da3d6 100644 --- a/use-cases/payment-detection.mdx +++ b/use-cases/payment-detection.mdx @@ -6,7 +6,7 @@ description: "Automatically detect and verify crypto payments with real-time blo ## Overview -Traditional crypto payments lack business context. You receive a transaction hash, but don't know which customer, invoice, or order it's for. Manual reconciliation is error-prone and doesn't scale. +Traditional crypto payments lack business context. You receive a transaction hash, but don't know which customer, invoice, or order it's for. Manual reconciliation is error-prone and doesn't scale. Request IDs solve this by attaching business context to every payment. Each request gets a unique Request ID that connects payments back to your specific invoice, order, or subscription with cryptographic certainty. @@ -72,7 +72,7 @@ These scenarios all use automatic payment detection. [See technical details on d - Customer sends payment to your wallet address - the Request ID is automatically included in the transaction + Customer sends payment to your wallet address - the Request ID is connected to the transaction From d1729ffc031edded4c8e5726c0eb0be13910468b Mon Sep 17 00:00:00 2001 From: MantisClone Date: Sat, 22 Nov 2025 09:19:55 -0500 Subject: [PATCH 11/12] Restructure Common Scenarios: 3 focused scenarios - Reorder to prioritize e-commerce checkout (canonical use case) - Remove donations scenario (too niche) - Strengthen remaining scenarios with clearer value props New order: 1. E-commerce Checkout - high-volume, single wallet, many customers 2. SaaS Subscriptions - recurring payments, automatic renewals 3. Manual Invoices - integration with existing workflows, variable amounts Each scenario now emphasizes distinct value proposition and use case pattern. --- use-cases/payment-detection.mdx | 21 ++++++++------------- 1 file changed, 8 insertions(+), 13 deletions(-) diff --git a/use-cases/payment-detection.mdx b/use-cases/payment-detection.mdx index 46da3d6..776e622 100644 --- a/use-cases/payment-detection.mdx +++ b/use-cases/payment-detection.mdx @@ -40,25 +40,20 @@ Request IDs solve this by attaching business context to every payment. Each requ ## Common Scenarios -### Donations with Attribution -Accept crypto donations to a single wallet and automatically attribute each to the correct donor, campaign, or cause. +### E-commerce Checkout +Accept crypto payments at scale without generating unique addresses for each customer. -**Example:** A nonprofit collects donations from hundreds of donors to one Ethereum address. Each donation is linked to a unique Request ID, enabling automatic attribution and thank-you emails. +**Example:** An e-commerce platform processes 10,000+ crypto orders per day. Each order gets a unique Request ID - customers pay to a single wallet address, and every payment is automatically attributed to the correct order. -### SaaS Adding Crypto Payments -Add crypto as a payment option to existing subscription or billing platforms alongside credit cards. +### SaaS Subscriptions +Add crypto as a payment option for recurring billing alongside traditional payment methods. -**Example:** A SaaS company uses Stripe for card payments but wants to offer USDC payments. Payment Detection monitors for crypto payments and updates subscription status automatically. +**Example:** A SaaS company uses Stripe for card payments but offers USDC for monthly subscriptions. Payment Detection automatically confirms renewals and updates subscription status without manual tracking. ### Manual Invoices with Crypto Settlement -Send invoices through existing channels (email, PDF) and let customers pay in crypto with automatic detection. +Send invoices through existing channels (email, PDF) and accept crypto payments with automatic reconciliation. -**Example:** A freelancer emails invoices as PDFs with a Request ID. When clients pay in crypto, the freelancer's accounting software automatically marks invoices as paid via webhook. - -### High-Volume Payment Collection -Collect thousands of payments without generating unique wallet addresses for each transaction. - -**Example:** An e-commerce platform processes 10,000+ crypto orders per day. Instead of unique addresses, each order gets a unique Request ID for attribution. +**Example:** A freelancer emails invoices as PDFs with a Request ID. When clients pay in crypto, the accounting software automatically marks invoices as paid via webhook - no manual checking required. These scenarios all use automatic payment detection. [See technical details on detection methods and configuration β†’](/api-features/payment-detection) From 91939ab2fde1bd0ee13f5da1fb7981f0cd143405 Mon Sep 17 00:00:00 2001 From: MantisClone Date: Sat, 22 Nov 2025 10:23:43 -0500 Subject: [PATCH 12/12] Refocus 'When to Use' section on problem signals Replace generic benefits with specific problem indicators: 1. Payment Collisions - Core technical problem (connects to welcome demo) 2. High Payment Volume - Scale problem where manual tracking fails 3. Wallet Management Overhead - Operational pain of separate wallets 4. Cross-chain Payments - Unified detection across chains without multiple APIs Each card now helps users self-identify if they have problems Payment Detection solves, rather than listing generic benefits. --- use-cases/payment-detection.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/use-cases/payment-detection.mdx b/use-cases/payment-detection.mdx index 776e622..eb85cf4 100644 --- a/use-cases/payment-detection.mdx +++ b/use-cases/payment-detection.mdx @@ -21,20 +21,20 @@ Request IDs solve this by attaching business context to every payment. Each requ ## When to Use Payment Detection - - You have invoicing, billing, or business systems and need to add crypto payment acceptance + + Multiple payments of the same amount create attribution problems - you can't tell which customer paid - - Collect thousands of payments to one wallet and automatically attribute each one + + Processing hundreds or thousands of crypto payments where manual tracking doesn't scale - - Get instant payment confirmation without manual blockchain monitoring + + Managing separate wallets for each customer or transaction creates operational complexity - - Accept payments across 9 EVM chains in 150+ currencies + + Accepting payments across multiple blockchains and need unified detection without managing multiple APIs