Commerce
Simulate a Commerce order transition (devnet only)
Advances a devnet commerce order to a specific state for integration testing.
Typical devnet flow:
- Create a checkout order + invoice via
POST /api/commerce/merchant/checkout/invoice(returnsorderId) - Simulate payment confirmation:
transitionTo=payment_confirmed - Simulate settlement (unlocks placement):
transitionTo=payment_settled - Simulate provider placement:
transitionTo=placed - Simulate tracking:
transitionTo=shipped(optionally includetracking) - Optionally simulate delivery:
transitionTo=delivery_confirmed
Notes:
payment_settledalso simulates provider submission (substatus=PROVIDER_PLACEMENT_SUBMITTED).failedcan only be simulated fromstatus=processing.cancelledcan only be simulated fromstatus=placed.refundedrequires a valid BSC refund destination (capture it at checkout or simulate payment usingwalletNetwork=bsc).
POST
Authorizations
Legacy alias for commerce-scoped API keys. Prefer x-api-key with scope=commerce.
Path Parameters
Body
application/json
Devnet-only request for simulating a commerce order transition.
Available options:
payment_confirmed, payment_settled, placed, shipped, delivery_confirmed, failed, cancelled, refunded Example:
"placed"
Optional tracking payload used for shipped/delivery transitions.
Optional payer wallet network used for payment simulation transitions.
Example:
"bsc"
Optional payer wallet address used for payment simulation transitions (must be EVM address for bsc).
Example:
"0x0000000000000000000000000000000000000001"

