Create direct order on behalf of a store
Partners create and process orders for a merchant using that merchant’s merchant-key, delivered to the partner in the store_onboarded webhook. The request body is identical to the standard Create Direct Order endpoint.
The merchant-key is what authorizes the call and what decides which store the order belongs to. Partner credentials may be sent alongside it for attribution, but never change the target store; on their own they are rejected with 403.
All payment gateways available to the merchant can be used.
Authorizations
Merchant key for store identification. Required for all API requests.
Body
Order amount. Must be greater than 0.
x >= 0.0150000
Order description displayed to the buyer during checkout.
1 - 255"Premium subscription - Monthly"
ISO 4217 currency code. Defaults to store currency if omitted.
3^[A-Z]{3}$"COP"
Buyer data. Required for Nequi and Daviplata direct orders, where email, phone_number, country, id_number and id_type must all be present (a missing one returns 422). Optional for Breb: omit it or send only the fields you have; fields you send are validated for format.
Your reference for this order, used to correlate Wava orders with your system. It is also the idempotency key of the order, scoped to your store: resending an order_key with the same amount and currency resolves to the existing order (an already paid one answers 200 with already_processed: true and starts no new payment), and resending it with a different amount or currency answers 409 ORDER_KEY_CONFLICT. Use a unique order_key per order.
100"order-12345"
URL to redirect buyer after successful payment.
"https://mystore.com/success"
URL to redirect buyer if payment is cancelled.
"https://mystore.com/cancel"
URL to redirect buyer if payment fails.
"https://mystore.com/error"
Device identifier for session tracking.
100"device-12345"
Response
Order created on behalf of store