Pays multiple payment requests in one transaction by either creating new requests or using existing request IDs. All requests must be on the same network. Supports mixed ERC20, Native, and conversion requests.
API key for authentication (optional if using Client ID)
Client ID for frontend authentication (optional if using API key)
Origin header (required for Client ID auth, automatically set by browser)
A list of payment requests to be created andprocessed in batch. All requests must be on the same network and contain payment/invoice currency information. Either requests or requestIds must be provided, but not both.
The request IDs of the existing requests to be paid. Requests must be on the same network. Either requests or requestIds must be provided, but not both.
The wallet address of the payer, user to check if approval is needed or not.
Batch payment calldata retrieved successfully
Array of ERC20 approval transactions needed before the batch payment. Only present when token approval is required.
The batch payment transaction for ERC20 tokens. Only present when the batch contains ERC20 payments.
The batch payment transaction for native ETH. Only present when the batch contains ETH payments.