Subscriptions and Recurring Payments (Recurring Billing) on a Website: How to Implement Them Technically

18.10.2026 Author: Victor Condratiuc, Founder of iLab.md

In Brief

A recurring payment is an automatic charge to a customer's card on a predefined schedule (monthly or annually), without requiring the customer to re-enter their card details or authorize each payment. Technically, there are two distinct mechanisms: saving a card for future payments initiated by the customer (one-click payments) and true recurring payments initiated automatically by the business without the customer's involvement at the time of the charge (known internationally as merchant-initiated transactions, or MIT). The card number is not stored on the website's server. Instead, the bank or payment processor provides a token linked to the card, which is used for all subsequent charges. In Moldova, among acquiring banks, only maib has publicly available official documentation specifically covering MIT recurring payments, including a dedicated API section for card registration and subsequent charges using a unique identifier. Victoriabank, MICB, and Fincombank do not offer equivalent public documentation for recurring payments. This does not necessarily mean that subscriptions cannot be implemented through these banks, but there is no publicly documented integration process comparable to maib's. The technical integration of recurring payments starts at €300 for a basic payment gateway connection (the same as for a one-time payment integration). Subscription management functionality — including payment scheduling, processing bank responses, managing subscription statuses, and sending failed-payment notifications — starts at an additional €300. The final cost depends on the complexity of the subscription plans.

Recurring Billing: Two Different Payment Mechanisms

Confusion around subscription implementation often arises because "saving a card for future payments" and "automatically charging a card every month" are two different features, both in terms of technical complexity and contractual requirements.

1. Saving a Card for Customer-Initiated Payments (One-Click)

The customer enters their card details once and completes authentication (3-D Secure — an additional verification code or confirmation through their banking app). The card is then stored as a token. During the next purchase, the customer does not need to enter their card number again, but they still initiate the payment by clicking the "Pay" button. Our portfolio includes an example of this functionality: in the EVPoint project (a network of electric vehicle charging stations), customers link their cards once. When topping up their balance again, they do not need to re-enter their card details, but they still initiate the top-up themselves.

2. Recurring Payments Without Customer Involvement at the Time of the Charge (MIT)

In this case, the business automatically initiates charges according to a predefined schedule — for example, on the first day of every month — without requiring the customer to visit the website or confirm the payment. This is what most people mean by a "subscription": Netflix, SaaS services, or gym memberships. Technically, a saved card token alone is not enough. The bank must support a separate transaction type explicitly identified as a recurring merchant-initiated transaction. Otherwise, the bank or payment network may flag a charge made without the customer's involvement as suspicious and decline it.

Tokenization: Why Card Numbers Are Not Stored on the Website

When registering a card, the customer enters their payment details on a secure page provided by the bank or payment processor, not on the online store's server — just as with a standard one-time payment. Instead of receiving the card number, the website receives a token (called billerId in maib's system). This identifier allows the bank to recognize which card should be charged, while the website cannot use it to retrieve the card number or CVV. As a result, integrating recurring payments does not necessarily introduce additional PCI DSS requirements (the security standard for handling payment card data) compared with standard one-time payments. The website can remain eligible for the simplified SAQ A category because card details are neither processed nor stored on its servers. Only the token is retained, and it cannot be used outside the specific banking system for which it was issued.

SCA and 3-D Secure: Why the First Payment Requires Authentication but Subsequent Payments Do Not

Under Strong Customer Authentication (SCA) requirements, which form part of the European PSD2 payment regulations, the first payment made with a new card must undergo strong authentication — typically through 3-D Secure, using an SMS verification code or confirmation in the customer's banking app. However, for payments initiated automatically by the business according to a predefined schedule (MIT), requiring 3-D Secure authentication for every charge would not only be inconvenient but also impractical: the customer is not present on the payment page to approve the transaction. Therefore, the initial payment and card registration are identified as the beginning of a recurring payment series and undergo full 3-D Secure authentication once. Subsequent automatic charges using the same card do not require repeated authentication. This approach is also reflected in maib's API: registering a card and processing subsequent charges are two separate API operations, and the latter does not require the customer to be present on the payment page.

In Moldova, Only maib Has Officially Documented Support for Recurring Payments

Of the four acquiring banks we examined in our article about integrating websites with maib, Victoriabank, MICB, and Fincombank, only maib provides a dedicated section of publicly available documentation for recurring payments. It describes separate API operations for registering a card and processing subsequent charges without customer involvement, as well as a separate one-click payment mechanism in which the customer confirms each transaction. Victoriabank, MICB, and Fincombank do not provide equivalent publicly accessible documentation specifically for recurring payments. This does not prove that implementing subscriptions through these banks is technically impossible — individual arrangements may be available upon request. However, unlike maib, they do not offer a clearly documented integration process with similarly predictable implementation requirements and timelines. In practice, for businesses in Moldova that need automatic subscription payments without requiring customers to take action every month, maib currently offers the most straightforward and predictable integration option.

What Makes Up a Subscription Billing System

Storing a card token is not enough. A subscription system also requires the logic to determine when payments should be collected, which customers should be charged, how much should be charged, and what should happen if a payment fails:

1. Payment Scheduler

An automated task checks each day which subscribers have reached their next billing date and initiates charges using their saved card tokens. In a PHP + CodeIgniter application, this is typically implemented using a server-side cron job that runs an application command once a day. For small and medium-sized subscriber bases, this is one of the simplest and most predictable solutions, without the need for a separate message queue service.

2. Processing Bank Callbacks

The bank communicates the result of a charge asynchronously, by sending a separate request to the website's server rather than necessarily returning the final result immediately in response to the payment request. The callback handler must be able to process duplicate notifications for the same payment. For example, a bank may send the same callback twice because of network issues. Without protection against duplicate processing, this could result in a payment being recorded twice or a customer's balance being credited more than once.

3. Subscription Statuses

A subscription needs clearly defined statuses rather than a simple "paid / unpaid" indicator: trial period, active, past due (the payment failed, but access has not yet been suspended), suspended, and canceled. The subscription status determines what the customer sees in their account and whether they can continue accessing the service.

4. Dunning: What Happens When a Payment Fails

A payment may fail for common reasons: the card has been blocked, has expired, or has insufficient funds. Immediately suspending access after the first failed attempt is generally not recommended, as some payments succeed when retried a day or two later. An effective approach involves several automated retry attempts at predefined intervals (for example, after 1, 3, and 7 days), notifying the customer after each failed attempt with a direct link to update their payment details, and suspending access only after all retry attempts have been exhausted.

5. Card Expiration

A token is linked to a specific card, and when that card expires, payments may stop going through even if sufficient funds are available in the account. This is one of the common causes of unexpected subscriber churn, even when customers have no intention of canceling their subscriptions. A practical solution is to notify customers 2–4 weeks before their cards expire and encourage them to update their payment method in their account, rather than waiting for the first failed transaction.

When to Use Subscriptions and When a Prepaid Balance Is Enough

  • Recurring payments (MIT) are appropriate when a business provides a periodic service with a fixed or predictable fee — SaaS access, memberships, or regular deliveries of the same set of products. In these cases, customers expect payments to happen automatically and do not want to visit the website every month.
  • A prepaid balance model (manual top-ups with charges based on actual usage) is simpler and often more convenient when the amount varies and depends on actual consumption — for example, electric vehicle charging or parking, where the final session cost is not known in advance. Customers do not need to confirm every small transaction, while a traditional subscription with a fixed recurring fee would not be suitable.
  • One-click payments without a full MIT subscription are sufficient when payments are repeated but irregular and initiated by customers themselves — for example, in an online store where returning customers simply want to avoid entering their card details for every purchase.

How We Implement These Features

When developing online stores or building mobile applications, we integrate payment systems directly into the PHP/CodeIgniter codebase rather than relying on ready-made modules provided by website builders. This is particularly important for recurring payments because payment scheduling, callback processing, and subscription status management require business-specific logic that cannot always be handled effectively by a universal plugin. We already have practical experience implementing saved-card functionality for repeat transactions: in the EVPoint project, customers link their cards once for future balance top-ups. Based on the same principles, we can develop a complete MIT subscription system with automatic scheduled charges through maib's API, tailored to each client's billing cycle and specific business requirements.

How Much Does Recurring Payment Integration Cost?

Basic payment gateway integration starts at €300, the same as for one-time payments. Additional subscription functionality — including payment scheduling, callback processing, subscription status management, dunning notifications for failed payments, and a subscription management section in the customer's account — starts at an additional €300. The final cost depends on the number of subscription plans, whether a trial period is required, and whether a separate subscriber management interface is needed. An exact quote is provided individually after reviewing the project's requirements.

  • Sources

Card Registration in the maib ecomm System — maib e-commerce API
maib-sdk-php — GitHub
What Are Merchant-Initiated Transactions (MIT)? — Checkout.com
Strong Customer Authentication (SCA) and PSD2 — Chargebee
Recurring Billing: How It Works, Benefits & Best Practices — Solidgate
Dunning Management: The Complete Guide — Baremetrics
PCI SSC — SAQ A Eligibility Criteria for Scripts

Join our Telegram channel Telegram channel