Use your gateway. Accept the way your customers already pay.

Keep the provider relationship and settlement flow that already works for your business. OrangeBee connects the gateway to the conversation instead of forcing every customer onto one payment provider.

• Vyapar Gateway for the currently proven QR workflow
• Razorpay, Paytm, PayPal, or another provider through a scoped adapter
• Workspace-level credentials kept outside the customer-facing browser

Provider availability and supported payment methods are confirmed during onboarding; integrations are not presented as live until their order and verification paths pass acceptance testing.

OrangeBee asks the connected provider for the payment experience it supports. UPI can stay QR-first inside WhatsApp, while cards, wallets, net banking, or PayPal can use the provider's approved checkout path.

• Scannable UPI QR image delivered in the originating chat
• Cards and alternative methods based on gateway capability
• Variable amounts and a unique order reference for every attempt

The existing payment flow is image-first for UPI QR because it is more reliable than depending on a WhatsApp payment link.

A generated QR is not a successful sale. OrangeBee checks the provider result and treats pending, success, failure, and timeout as different states before it updates the customer or your team.

• Gateway-verified status before a success message
• UTR or provider reference included only when available
• Duplicate callback and repeated-confirmation protection

The order stays linked to the workspace, conversation, and customer who requested it. A verified result returns to that customer and becomes available for sales attribution and follow-up.

• No group or broadcast delivery
• Conversation-bound amount, order, and status
• Human review and recovery for failed or expired attempts