Billing guide

Recurring payments and subscriptions in Qatar

Updated September 2026

Subscription revenue looks simple until the second month, when a percentage of your customers silently stop paying because a card expired and nobody noticed. Recurring billing is less about taking the first payment than about surviving the renewals.

This is how the mechanics work, what is specific to Qatar, and what to establish with a provider before you design your billing.

How a recurring card payment actually works

You do not store the customer’s card. Your provider stores it and gives you a token, an opaque reference that only works on your account. Your system keeps the token, the amount and the schedule, and asks the provider to charge the token when a renewal is due.

That distinction matters for compliance and for risk. A token in your database is not card data, so a breach of your systems does not expose card numbers.

The first payment is a different animal

The first charge is customer-initiated: they are present, they authenticate, and in this region that means a step-up with a one-time code. Later renewals are merchant-initiated: the customer is asleep, and there is nobody to type a code.

This is why the first transaction has to be set up correctly as the start of a series rather than as a one-off charge. If it is not, renewals can be refused because the issuer sees an unauthenticated transaction with no mandate behind it. Ask your provider explicitly how they flag the initial transaction and subsequent ones, before you build anything.

Get this wrong and everything works perfectly in testing and starts failing in month two, on live customers, in a way that looks like a mysterious decline problem.

Failed renewals are the whole game

Most subscription churn is not a decision. It is a card that expired, a card that was reissued after a fraud incident, or a balance that was short on the day you happened to charge. The customer still wants your product.

The recovery process, usually called dunning, is worth more attention than the sign-up flow:

  • Retry on a schedule that spreads across days and dates rather than hammering the same card
  • Tell the customer in their language, with a link to update the card, on the same day it fails
  • Do not cut off access at the first failure; a short grace period recovers a meaningful share
  • Watch for expiring cards before they expire and prompt for an update in advance
  • Treat a hard decline differently from a soft one: a closed account needs a new card, not a fourth retry

What is specific to Qatar

Two things shape recurring billing here. The first is that authentication expectations are high on the initial payment, which makes the flagging of the initial transaction more important than in markets where step-up is rare.

The second is the mix of methods. Qatar Central Bank’s December 2025 statistics put point-of-sale cards at 49% of payment value, the Fawran instant payment system at 25%, e-commerce at 24% and mobile wallets at 2%. Cards are the rail that supports card-on-file recurring billing; an instant bank transfer is generally a push payment initiated by the customer, which suits invoicing on a schedule rather than silent automatic renewal.

For business customers on larger amounts, a recurring invoice with a payment link is often the more realistic design than a stored card.

What to ask a provider before you build

  • Do you support tokenised card-on-file, and is the token portable if I change provider?
  • How do you flag the initial transaction in a series, and what do you send on renewals?
  • What happens to a stored token when the customer’s card is reissued?
  • Do you provide retry and dunning tooling, or am I building that?
  • Can I run a recurring invoice with a payment link as an alternative for larger business customers?
  • What reporting do I get on failed renewals specifically, rather than failed payments in general?

Where Rapid Gateway fits

Rapid Gateway gives Qatari merchants card acceptance with 3-D Secure, local payment methods, and a merchant portal with invoicing, so a scheduled invoice with a payment link is available today for customers you bill on a cycle.

If your business is subscription-based, say so in your application. We would rather map your billing model during onboarding than have you discover a gap in month two.

Frequently asked questions

How do recurring card payments work?

Your provider stores the card and gives you a token, an opaque reference that only works on your account. You store the token, amount and schedule, and ask the provider to charge the token when a renewal is due. You never store card data yourself.

Why do renewals fail when the first payment worked?

Usually because the first transaction was not set up as the start of a series. The first payment is customer-initiated and authenticated; renewals are merchant-initiated with nobody present to authenticate. If the initial transaction is not flagged correctly, issuers can refuse the renewals.

What is dunning?

The process of recovering failed renewals: scheduled retries, notifying the customer with a link to update their card, and a grace period before access is cut off. Most subscription churn is an expired or reissued card rather than a decision to leave.

Can I use Fawran for subscriptions?

Fawran is generally a push payment the customer initiates or approves, so it suits a recurring invoice with a request to pay rather than silent automatic renewal. Card-on-file is the rail for unattended recurring charges.

Do I need to store card numbers to bill customers monthly?

No, and you should not. The provider stores the card and gives you a token. A breach of your systems then exposes tokens that are useless anywhere else, not card numbers.

What is the best approach for larger business customers?

A recurring invoice with a payment link is often more realistic than a stored card for larger amounts, because it gives the customer’s finance team a document and a reference to process.

Bill on a schedule without losing customers to expired cards

Apply to Rapid Gateway and tell us how you bill; we will map it during onboarding.

Get started