BASE NETWORK

Base payments for Base-aligned buyers.

recv adds Base One to your payment stack with the same checkout, invoice, and webhook model used across supported networks.

L2 PAYMENT

payment.network.arbitrum

249.00 USDT
RailBase One
AssetsERC-20 USDT
SettlementDirect
SUPPORTED ASSETS

Base-native USDT payments.

Use Base for customers who want Base-compatible assets with lower transaction costs than mainnet.

01

USDT on Base

USDT stablecoin transfer on Base One layer 2 for highly scalable USD-denominated payments.

WHY BASE

Base alignment without mainnet costs.

Base is a practical option for EVM-native customers who prefer Base tooling but need lower fees for routine payments.

LIMITATIONS AND NOTES

Base One is separate from mainnet and other L2s.

Payments must be sent on Base One. Base, Base, BSC, or other EVM transfers are different rails and will not be treated as the same payment automatically.

CHECKOUT AND API MECHANICS

Normalized events for Base transfers.

01

Create invoice

Use recv Checkout or API with Base One as the payable network.

02

Guide payment

The buyer sees Base-specific address, amount, asset, and QR instructions.

03

Monitor transfer

recv watchers detect native and ERC-20 transfers on Base One.

04

Sync backend

Signed webhooks update your order or billing system with the same event shape as other networks.

RELEVANT USE CASES

Best for EVM-native businesses.

Base works well for teams whose buyers already operate in Base L2 environments.

01

API payments

Add Base to backend-driven invoice and webhook flows.

02

Business billing

Collect stablecoin invoices from Base-aligned customers.

03

Web3 services

Support buyers who prefer L2 settlement for recurring or one-time services.

Add Base payments to your checkout stack.

Use recv to accept Base One payments, monitor transfers, and keep settlement direct to your wallet.