Gateway Discovery
Before creating any order, you need to know which payment gateways are active for your store and what fields each gateway requires from the buyer.Why this step matters
Each store has different payment gateways enabled depending on their configuration. The gateway discovery endpoint returns the exact list of available gateways, their IDs, and the required fields — so your integration adapts automatically without hardcoding gateway details.Request
Response
The response includes an array of available gateways with their configuration:How to use the response
1
Call the endpoint
Make a
GET /v1/orders/paymentGateways request with your merchant-key header.2
Display available gateways
Show the buyer only the gateways returned in the response. Use the provided
gateway_logo URLs for gateway logos. For Direct Orders, only offer gateways with supports_direct_api: true.3
Collect required fields
Nequi and Daviplata direct orders need the shopper fields described in Creating Orders; for Breb the
shopper object is optional. On top of that, use the flags to know what the selected gateway uses: requires_phone (Nequi) or required_shopper_national_id (Daviplata).4
Create the order
Pass the
id_payment_gateway and collected fields to POST /v1/orders. See Creating Orders for the full request format.Gateway-specific required fields
For gateway-specific payment flows (push notifications, OTP, QR codes), see Payment Flows.