MyFatoorah + WhatsApp Integration
Kuwait’s default invoice and checkout rail: generate MyFatoorah payment links in chat, then fire Utility templates when KNET, Apple Pay, or card capture succeeds.
MyFatoorah is the payment stack Kuwaiti ecommerce, clinics, and tuition desks already run. Ominiflow generates a MyFatoorah invoice or payment-link URL from chatbot or template variables (amount in KWD, invoice ID, customer mobile) and sends it as an approved Utility button. The customer pays on MyFatoorah — KNET, Apple Pay, Visa/Mastercard — then a webhook on successful capture triggers the receipt template and closes the 24-hour window with a service reply if they write back.
This is the Kuwait replacement for Razorpay. Do not send UPI or INR checkout to a +965 number. Pair with Arabic and English template pairs, and keep the invoice PDF or receipt URL in the same thread so CITRA/CBK-aware teams have an audit trail.
Typical volume: D2C checkout recovery, restaurant prepay, school fee collection, and clinic deposits in Kuwait City, Salmiya, and Hawally. Shopify and WooCommerce stores already on MyFatoorah can reuse the same invoice API from Ominiflow workflows.
How It Works
-
1
Connect MyFatoorah APIAdd vendor token / API key from the MyFatoorah dashboard into Ominiflow payment integrations. Use the Kuwait endpoint, not the test token, for live KNET.
-
2
Create a payment-link templateApproved Utility template with a dynamic URL button. Map amount, invoiceId, and customer name from the chatbot or CRM.
-
3
Subscribe to capture webhooksPoint MyFatoorah success/failure callbacks at the Ominiflow endpoint. Fire receipt on paid; retry sequence on failed or expired KNET session.
-
4
Test with a KWD 0.100 invoicePay with a real KNET test card, confirm the WhatsApp receipt, then enable production for +965 numbers.