Settle IPP receipts
Availability
Merchant routes for settlement-item listing and settlement retrieval and listing are confirmed. Funds execution support for creating settlements remains unconfirmed. Queryable tasks or a create control do not establish that the environment can complete settlement. Confirm access to the full execution flow first.
Settlement moves received IPP funds in full to the wallet fixed by the original receipt. It is not a bank payout and does not allow an arbitrary recipient. Direct ERC-20 transfers are not IPP settlement items. Record payment completion, funds becoming available and final settlement separately.
Inspect the funds first
- Trace the original receipt from the order and query settlement items by network, currency and account environment. Only finalized IPP funds enter this list.
- Distinguish
available,in_progressandsettled; reserved items are not available for another settlement. - Check the receipt, item ID, precise amount, network, currency and fixed recipient wallet. Separate incompatible combinations rather than merging matching token symbols.
- Check existing tasks and continue tracking them. Until execution support is confirmed, limit work to queries and reconciliation preparation.
After execution is confirmed
- Select compatible
availableitems. Follow current network, currency and recipient compatibility rules and system validation; do not substitute a new recipient. - Have the integration owner persist the selected items and idempotency key, create the task and save its Settlement ID. Do not select reserved items again.
- Wait through
preparing. Atrequires_action, retrieve the original task again and use the latestnext_action. - Check the wallet account and network. Preserve the supplied
from,to,dataandvalue; let the wallet estimate Gas. Do not edit transaction parameters or execute illustrative transactions. - Sign and send from the merchant wallet, retaining the transaction hash and task ID. The platform detects a matching transaction without a separate hash-confirmation submission.
- Query until
succeeded, then reconcile the items and final record. “Sent” or a transaction hash alone does not establish final settlement.
After creation, the amount, items, network, currency and recipient are immutable, and there is no cancellation API. Do not wait for automatic settlement or timed release of the task.
Recover a stalled operation
| State or situation | Action |
|---|---|
preparing | Query the original task; items are reserved |
requires_action, not sent | Continue with the latest transaction; rejecting a signature does not release items |
Sent but still requires_action | Inspect the original transaction; delayed observation does not justify resending |
processing | Await finalized confirmation without resending or creating another task |
succeeded | Record the final state and completion time |
failed | Preparation failed and items were released; refresh actual availability before deciding on another task |
| HTTP or broadcast timeout, or temporarily missing result | Keep the result unknown and inspect the original task and transaction; do not infer failure or released items |
Prepare another execution only when the platform explicitly returns to requires_action with a new transaction. No minimum, automatic frequency, subsidy or completion time is promised here. See wallets and fees.