Endpoint
Verify that a blockchain payment transaction meets the expected criteria.The blockchain transaction hash (must start with 0x, 66 characters) Example:
0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdefBlockchain network:
base (Base Mainnet) or base-sepolia (Base Sepolia Testnet)The seller’s blockchain address (42 characters, must start with 0x) Example:
0x742d35cc6634c0532925a3b844bc9e7595f0beb0Expected payment amount in wei (as string to avoid precision loss) Example:
"1000000000000000000" (1 ETH in wei)Expected token contract address for ERC20 payments. Use
null for native
token (ETH, MATIC, etc.) Example: 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48
(USDC)Additional metadata for the transaction
URL to receive settlement status updates. Must be HTTPS in production.
Example:
https://your-app.com/webhooks/settlementHeaders
Your API key for authentication
Unique key to prevent duplicate verifications. Valid for 24 hours. Example:
verify_ORDER-123_1234567890Response Fields
Unique identifier for this verification. Use this for settlement.
Verification status:
verified, pending, failed, or rejectedThe verified transaction hash
The blockchain network
Actual verified amount in wei (null if pending)
Verified token contract address (null for native token)
ISO 8601 timestamp when verification completed
Additional verification details (confirmations, block number, etc.)
Common Use Cases
Native Token Payment (ETH, MATIC)
Native Token Payment (ETH, MATIC)
ERC20 Token Payment (USDC, DAI)
ERC20 Token Payment (USDC, DAI)
With Webhook Notification
With Webhook Notification
Verifications are processed in less than 2 seconds. Background workers handle
transaction logging asynchronously.