PaymentsTap Payments WhatsApp Integration
KNET, benefit, mada and cards, collected in the conversation.
Tap is built for the Gulf, and that shows in the payment methods customers actually reach for — local debit schemes as well as international cards. Connect your Tap account and the chatbot's payment block raises a Tap link for the amount the flow holds, waits for confirmation, and carries on down the branch that matches the outcome.
Libromi Connect
WhatsApp Business Platform
Tap Payments
Two-way connection
Where it shows up
- Payment block
- Chatbot builder node
- WhatsApp store & catalogue
Local debit customers who cannot pay you
In much of the Gulf, a meaningful share of customers pay with a local debit scheme rather than an international card. If your checkout does not offer it, those customers do not convert — and in a chat sale they simply stop replying, which looks like disinterest rather than a payment problem.
What moves, and which way
Tap to WhatsApp
Confirmed payments
Tap confirms the transaction and the flow continues, with no manual verification.
Failed or abandoned
Unsuccessful attempts take their own branch so the customer can retry or choose another method.
Transaction reference
Available to later steps for receipts, order records or a CRM write.
WhatsApp to Tap
Payment links
Raised on your own Tap account for the amount and reference the flow supplies.
Cart and quote totals
The amount comes from a connected store's total or a value agreed in the conversation.
Contact details
The conversation's contact travels with the request.
Settlement is to your own Tap merchant account, under your existing terms.
What you get
Gulf payment methods
Offer the local schemes your customers use alongside international cards, from one link.
Automatic confirmation
The flow only proceeds when Tap says the payment cleared.
Separate paths per outcome
Paid, timed out and cancelled are distinct branches, so nothing is assumed.
Store checkout supported
WhatsApp store orders can settle through Tap with tax and delivery already applied.
What you can build with it
Chat checkout for a GCC store
The customer browses, orders and pays in one conversation using the method they normally would.
Prepayment for reservations
Confirm the reservation only once Tap verifies the payment.
Split follow-up by outcome
A cancelled payment triggers a different message than a timeout, so the retry is actually helpful.
A Kuwaiti restaurant group taking catering orders
Catering enquiries arrived on WhatsApp and were confirmed by bank transfer, which meant chasing receipts and manually matching them to orders. Customers who wanted to pay by local debit had no easy option.
The result
No more transfer receipts to match, and customers pay with the method they were always going to use.
- 1
The chatbot collects the menu, headcount and date and calculates the total.
- 2
The payment block raises a Tap link for the deposit, payable by local debit or card.
- 3
Tap confirms and the order is locked in, with the kitchen notified automatically.
- 4
The balance link goes out closer to the date from the same conversation.
How to connect it
- 1
Connect Tap
Add your Tap merchant credentials in Libromi Connect.
- 2
Add the payment block
Set the amount from the flow's own values and give it a clear reference.
- 3
Build the branches
Handle paid, timed out and cancelled so every conversation has somewhere to go.
Frequently asked questions
Related integrations
Teams that connect this one usually connect these too.
Take the payment they were going to make anyway
Connect Tap and finish the sale inside the chat.