How does a BenefitPay payment work?
The shopper chooses BenefitPay at checkout. On a website, payment providers such as Tap Payments show a BenefitPay button; clicking it displays a QR code that opens the BenefitPay app, where the shopper reviews the amount and confirms. The app itself is tied to the shopper’s Bahraini bank cards and accounts: when BENEFIT launched it, users registered with their personal number (CPR) and mobile number, confirmed with a one-time SMS code and approved payments with a PIN or fingerprint.
The result reaches the merchant through the provider. Tap’s web integration fires a success, cancel or error callback in the browser and posts the transaction status to a webhook URL on the merchant’s server. Payments are in Bahraini dinars only, with three decimal places, and Tap states that BenefitPay does not support a separate authorisation step, so each payment is a direct sale.
Merchants join through a provider or bank. At launch, BENEFIT said merchants would contact their acquiring bank to get login credentials for the merchant side of the app. For online checkout, Tap requires the merchant’s domain to be registered with it before the BenefitPay button works, and issues a public key for that domain.
Why does BenefitPay matter for merchants?
BenefitPay is where Bahraini residents already move money. BENEFIT reported 466 million transactions worth BD 10.2 billion through the app across its Fawri, Fawri+ and Fawateer services in 2025, up 10.6% in volume. In the first half of 2026 the app carried 246 million transactions worth BD 5.4 billion, up 7.2% on a year earlier, out of 261.2 million across all channels.
Most of that is Fawri+, the near-instant transfer service: 455.3 million of the app’s 2025 transactions used it. BENEFIT raised the Fawri+ daily limit from BD 1,000 to BD 3,000 per bank account during 2025, and launched a Business Account so that single-owner businesses can send and receive payments in the app.
For an online shop, that familiarity matters. A shopper who already pays bills and friends through BenefitPay can pay a merchant the same way, without typing card details.
What can go wrong?
The QR step suits desktop more than mobile. The web flow Tap documents shows a QR code, which works for a shopper at a computer with a phone in hand. Merchants should test how their provider handles a shopper who is already on their phone before launch.
Refund support is not uniform. Tap’s BenefitPay documentation does not cover refunds, and third-party payment guides describe them differently, so a merchant should confirm with its provider whether full and partial refunds are available and how long they take before relying on them for returns.
Disputes are not documented as a card-style chargeback process. Clear order and delivery records remain the main defence if a shopper complains through their bank.
Status must come from the server. The browser callback can be lost if the shopper closes the page after paying in the app, so the order should be released on the webhook or a status check, not on the redirect.
Foreign shoppers cannot use it. BenefitPay is linked to Bahraini bank accounts and cards, so visitors need an international card option.
How would Omno handle BenefitPay?
BenefitPay would be shown in the hosted checkout as its own method, separate from BENEFIT debit cards, and only for BHD orders. The merchant’s routing rules would send it only to providers that support the wallet. If the chosen provider were unavailable or rejected the request, the payment would move to the next provider in the rule until one accepts. Payment status would be tracked from pending to final, and the final result would arrive by webhook, which is the source of truth for releasing an order. The routing-decision log would record which provider handled each payment.