Creating Orders

Creating Orders as a Partner

Once a merchant has connected to your platform you hold their merchant_key, delivered in the store_onboarded webhook. That key is all you need: the request is byte-for-byte the same as a standard order creation.

The merchant key is what authorizes this call and what decides which store the order belongs to. You may add your X-API-Key/X-API-Secret for attribution, but they never change the target store. See Partner Authentication.

Example

curl -X POST "https://api.wava.co/v1/orders" \
  -H "merchant-key: MERCHANT_KEY_FROM_STORE_ONBOARDED" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 50000,
    "description": "Product purchase",
    "currency": "COP",
    "shopper": {
      "first_name": "Juan",
      "last_name": "Perez",
      "email": "juan@email.com",
      "phone_number": "+573001234567",
      "country": "CO"
    },
    "payment_gateway": {
      "id_payment_gateway": 1
    },
    "order_key": "partner-order-001"
  }'

The response is identical to a direct merchant order, and all payment flows (Nequi, Daviplata, Breb) behave identically.

Tracking the order back to your system

order_key is echoed back to you as id_external in webhooks. Use it to match the order to your own record.

Available payment gateways differ per merchant. Call gateway discovery with that merchant’s key rather than hardcoding id_payment_gateway.

When the order is paid, order_payment is delivered to your partner webhook URL, not the merchant’s. See Partner Webhooks.

For the full request body reference see Creating Orders; for gateway-specific flows see Payment Flows.

Getting Started

Orders

Payment Flows

Payment Links

Partners

Webhooks

Integrations

Testing

Error Handling

Creating Orders as a Partner

Example

Tracking the order back to your system

​Creating Orders as a Partner

​Example

​Tracking the order back to your system

Creating Orders as a Partner

Example

Tracking the order back to your system