WhatsApp Payments on the Business API in India 2026: order_details vs Checkout payment-mode

On WhatsApp Business API in India, “payments” can mean two different things. Gateway pay uses Meta interactive order_details (Review and Pay) with a linked payment configuration such as PayU or Razorpay. Checkout Flow “UPI / Card / COD” fields only record a payment-mode preference with address data—they do not capture money through a PG. ChatYug documents both paths: product overview at /whatsapp-payments and API detail at WhatsApp Payments docs.

Two meanings of “WhatsApp payments”

Operators often mix gateway capture with checkout preference. Treating a Flow dropdown as PayU/Razorpay checkout causes failed expectations. Decide first: do you need money collected inside WhatsApp, or only COD/UPI preference plus address?

Gateway pay: interactive order_details

Link a payment partner account to the WABA in Meta WhatsApp Manager, optionally save configuration_name in ChatYug, then send interactive order_details inside the 24-hour window via ChatYug External API. Payment webhooks and order_status updates complete the loop. Outside the window, use an approved ORDER_DETAILS template with an orderDetails payload. Supported gateway configurations documented by ChatYug include PayU, Razorpay, BillDesk, and Zaakpay.

Checkout Flow payment-mode (not gateway pay)

After Meta catalog cart, ChatYug can send a checkout WhatsApp Flow that collects address and a payment-mode preference (including COD). That field is text/preference for fulfilment—not a card or UPI charge. See Checkout & Flow Design and WhatsApp Commerce.

Which path to use

Use checkout Flow when COD and address capture are the goal. Use order_details / ORDER_DETAILS templates when you need prepaid capture inside WhatsApp. Many Indian brands run COD first, then add gateway pay for prepaid SKUs.

Need Path
Address + COD / UPI preferenceCheckout Flow payment-mode
Charge via linked PG in WhatsAppInteractive order_details (24h) or ORDER_DETAILS template
Fulfilment status after payorder_status API

Prerequisites for gateway pay

Meta payment configuration on the WABA, a ChatYug API key for External API calls, and correct session handling. If interactive send returns outside-session errors, open with an approved template first—do not bypass Meta rules with unofficial tooling.

FAQ

What is WhatsApp order_details payment?

Meta Review and Pay via a linked payment gateway configuration on the WABA.

Is checkout Flow UPI/Card the same as gateway payment?

No. It is a preference field with address collection, not PG capture.

Can I send order_details outside the 24-hour window?

Use an approved ORDER_DETAILS template (or open a session first). Interactive order_details is for the 24h window.

Which path should COD-heavy brands use?

Checkout Flow for address + COD preference; add order_details when prepaid inside WhatsApp is required.

Where is ChatYug WhatsApp Payments documented?

/whatsapp-payments and developer docs.

Set up gateway pay or checkout preference Flows on the official WhatsApp Business API with ChatYug.

WhatsApp Payments Pricing