> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wava.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment Flows

> How each payment gateway works from order creation to confirmation.

# Payment Flows

Each payment gateway has a different flow for how the buyer completes their payment. This section explains the end-to-end process for each gateway.

## Available gateways

<CardGroup cols={2}>
  <Card title="Nequi" icon="mobile" href="/payment-flows/nequi">
    Push notification flow. Buyer approves payment in the Nequi app.
  </Card>

  <Card title="Daviplata" icon="message-sms" href="/payment-flows/daviplata">
    OTP verification flow. Buyer receives a code via SMS and submits it.
  </Card>

  <Card title="Breb" icon="qrcode" href="/payment-flows/breb">
    QR code / transfer key flow. Buyer completes a bank transfer.
  </Card>

  <Card title="Stripe" icon="stripe" href="/payment-flows/stripe">
    Card payment flow. Configured through the Wava dashboard.
  </Card>
</CardGroup>

## Order lifecycle

All payment gateways follow the same order status progression:

```mermaid theme={null}
stateDiagram-v2
    [*] --> pending: Order created
    pending --> processing: Payment initiated
    processing --> confirmed: Payment successful
    processing --> cancelled: Rejected / Timeout
    confirmed --> refunded: Refund processed
```

| Status       | Description                                                                                  |
| ------------ | -------------------------------------------------------------------------------------------- |
| `pending`    | Order has been created but payment has not yet been initiated with the gateway.              |
| `processing` | Payment is in progress — waiting for buyer action (push approval, OTP, transfer).            |
| `confirmed`  | Payment completed successfully. Funds will be included in your next payout.                  |
| `cancelled`  | Order was cancelled — buyer rejected the payment, it timed out, or it was cancelled via API. |
| `refunded`   | A refund has been processed for this order.                                                  |

## Gateway discovery

Before creating orders, call `GET /v1/orders/paymentGateways` to determine which gateways are active for your store and what fields each requires.

```bash theme={null}
curl -X GET "https://api.wava.co/v1/orders/paymentGateways" \
  -H "merchant-key: YOUR_MERCHANT_KEY"
```

## Webhooks

For Nequi and Breb, the buyer completes payment asynchronously. Use [webhooks](/webhooks/overview) to receive real-time status updates, or poll `GET /v1/orders/{orderId}`.

## UX requirements

All implementations must be reviewed and approved by the Wava team before going live. You must display:

* **Payment gateway logos** using official assets provided by Wava
* **Processing animations** using official Wava GIFs showing step-by-step payment flows
* **User-facing instructions** in Spanish, guiding the buyer through each step

See each gateway's page below for specific UX assets and copy.