Skip to content

Custom invoices

create_invoice gives full control over each invoice.

paymentCurrency is a Request Network currency ID in the form SYMBOL-network:

Currency ID Meaning
USDC-mainnet USDC on Ethereum
USDC-base USDC on Base
USDCn-matic USDC on Polygon
USDC-arbitrum-one USDC on Arbitrum
fUSDC-sepolia Test USDC on Sepolia
ETH-sepolia-sepolia Test ETH on Sepolia

Not sure? Ask “what’s the currency ID for USDT on Arbitrum?” and the assistant uses find_currency.

Set invoiceCurrency to USD:

Invoice 0xAb…12 $1,200 for March consulting, paid in USDC on Base, reference INV-042.

{
"amount": "1200",
"invoiceCurrency": "USD",
"paymentCurrency": "USDC-base",
"payee": "0xYourWallet",
"reference": "INV-042"
}

payee defaults to REQUEST_PAYEE, then to the wallet of your route on the same network. With a Client ID and no payee, the route’s wallet is used.

Unlike payment links, custom invoices aren’t tied to your route’s network: a Client ID made on a Sepolia route created a USDC invoice on Base in our testing. Name the token and network in paymentCurrency.

For retainers and subscriptions:

Bill Acme 500 USDC on Base every month, starting December 1.

create_invoice takes repeat (daily, weekly, monthly, quarterly, yearly) and an optional startDate (today or later; defaults to today). Request Network creates a new invoice each period; each one shows up in list_invoices and is paid on its own.

Stop billing Acme every month.

stop_recurring_invoice stops it; invoices already created stay as they are. Say “resume” to restart it.

Recurring billing works with custom invoices only; payment links are one-off.

The payer uses get_payment_transactions or any Request-compatible app with the invoice ID.