List payer transactions
This operation retrieves on-chain transactions related to a specific top-up payer.
You need to specify custom_payer_id, which is the merchant-defined customer identifier used when creating top-up addresses.
For more information, see Cobo Payments Guide.
Documentation Index
Fetch the complete documentation index at: https://cobo.com/payments/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
The API key. For more details, refer to API key.
In the API playground, enter your API secret, and your API key will be accordingly calculated.
Query Parameters
The maximum number of objects to return. For most operations, the value range is [1, 50].
A cursor indicating the position before the current page. This value is generated by Cobo and returned in the response. If you are paginating forward from the beginning, you do not need to provide it on the first request. When paginating backward (to the previous page), you should pass the before value returned from the last response.
A cursor indicating the position after the current page. This value is generated by Cobo and returned in the response. You do not need to provide it on the first request. When paginating forward (to the next page), you should pass the after value returned from the last response.
The merchant ID.
Unique customer identifier on the merchant side, used to allocate a dedicated top-up address
The token ID, which is a unique identifier that specifies both the blockchain network and cryptocurrency token in the format {CHAIN}_{TOKEN}. Supported values include:
- USDC:
ETH_USDC,ARBITRUM_USDCOIN,SOL_USDC,BASE_USDC,MATIC_USDC2,BSC_USDC - USDT:
TRON_USDT,ETH_USDT,ARBITRUM_USDT,SOL_USDT,BASE_USDT,MATIC_USDT,BSC_USDT
A list of transaction hashes, separated by comma.
A list of transaction IDs, separated by comma.
