Transfer requests
In order to process transfers, a transfer request needs to be created and signed for each transfer request and sent to Loop’s API.
Each transfer request must have its transfer details signed by a dedicated signer wallet whose address is configured in the contract. This is to ensure that none of the transfer details are changed at any point between the time they are sent to Loop and the time they are executed in the contract. See the Signing transfer requests section for details on how to sign transfer requests.
Each transfer request also has a bill date property which allows transfer requests to be submitted either for processing immediately (bill date of 0) or for processing on or after the the bill date specified.
Multiple transfer requests can be submitted in the same request.
Transfer requests must be sent by the Sunday before the intended billing date for reminders to go out.
The unique identifier for a given invoice from your invoice system (e.g. Stripe, Chargify)
"ch_3Ljpa52eZvKYlo2C1VHbn91O"
The amount to transfer, denominated either in USD if field usd is set to true or the given token (including decimals)
"1000000000"
The address of the ERC20 token being transferred
"0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48"
Whether or not the amount is denominated in USD or the given token. If denominated in USD, the amount will be converted to the token amount at the time of processing. The exchange rate is retrieved from an on-chain Chainlink oracle. Conducting this conversion on-chain costs gas, thus consider only using this feature if converting from a non-stable coin (e.g. WETH).
false
The ID of the item this transfer relates to.
"a3effd58-7e10-4012-8917-329cc882f79d"
The approximate time at which to process the given transfer request. This needs to be formatted as a Unix timestamp in seconds. If 0, the transfer request will be processed "immediately" (as soon as the Loop bot network picks it up)
1664096943
The address receiving the transfer
"0x0f2672BA12aed17BEe075F7AEabC24b98E3098Ca"
The address sending the transfer
"0xad4efce746f129a9df375af2ddcf9097531eb466"
A signature of the above 6 parameters
"0x7c4e1650d88f08e24f..."
The ID of the entity the payment relates to
"97f41ed9-cf70-4548-b5aa-88f0083e3305"
The network to process the given transaction on. 1: “mainnet”, 5: “goerli”, 56: “bnb”, 97: “chapel (BNB testnet)”, 137: “polygon”, 42161: “arbitrum”, 80001: “mumbai (Polygon testnet)”
5
A list of tag IDs to associate with the transfer
Additional comments from the transfer initiator
Ok
Last updated