Skip to main content

Overview

Traditional crypto payments lack business context. You receive a 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. What you get:
  • 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 - for instant payment confirmations
  • Zero manual work - No spreadsheets, no guessing, no payment collisions
See how Request IDs prevent payment collisions (welcome page demo) →

When to Use Payment Detection

Payment Collisions

Multiple payments of the same amount create attribution problems - you can’t tell which customer paid

High Payment Volume

Processing hundreds or thousands of crypto payments where manual tracking doesn’t scale

Wallet Management Overhead

Managing separate wallets for each customer or transaction creates operational complexity

Cross-chain Payments

Accepting payments across multiple blockchains and need unified detection without managing multiple APIs

Common Scenarios

E-commerce Checkout

Accept crypto payments at scale without generating unique addresses for each customer. 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 Subscriptions

Add crypto as a payment option for recurring billing alongside traditional payment methods. 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 accept crypto payments with automatic reconciliation. 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 - no manual checking required.
These scenarios all use automatic payment detection. See technical details on detection methods and configuration →

How Payment Detection Works

1

Create Request

When you create a request, it gets a unique Request ID for tracking
2

Customer Pays

Customer sends payment to your wallet address - the Request ID is connected to the transaction
3

Automatic Detection

Request Network monitors and matches payments to your requests
4

Get Notified

When a payment is detected, you receive a notification with payment details

Key API Features for Payment Detection

What’s Next?