Paymob

Paymob sits between a merchant and the banks and wallet providers. The merchant creates an order through Paymob's API or dashboard, the customer pays with a card, a mobile wallet, or an instalment option at checkout, and Paymob settles the money to the merchant's bank account. For developers the two important pieces are the payment API, which returns a hosted checkout page or a payment link for any amount, and the transaction callback (webhook) that Paymob sends to a URL you register when a payment succeeds or fails. That callback is what lets an external system mark an order as paid without a person checking the dashboard.

In Egypt, where card penetration is lower than in the Gulf and mobile wallets are widely used, a gateway that accepts both is the difference between a completed sale and a customer who says 'I will pay on delivery' and then cancels. Paymob started in Egypt and has since expanded into Gulf markets, which matters for merchants selling in more than one country. The most useful pattern for service businesses is the payment link: a clinic, a course provider or a shop sends the link inside a WhatsApp conversation, the customer pays on the phone, and the webhook confirms it in seconds.

Nano AI lists Paymob among the integrations of its WhatsApp AI agents: the agent creates the payment link for a booking deposit or an order, sends it in the chat, waits for the Paymob callback, and only then confirms the appointment or triggers fulfilment, with any dispute routed to a human. If you are wiring Paymob into an AI flow, insist that the agent never marks anything paid on the customer's word, that the webhook signature is verified, and that card details are never typed into the chat.