Regular\recurring payments version 2.0

The module helps to work out and implement the business logic of recurrent payments.

Development of the logic of regular payments

Today, many services and digital goods are provided by subscription: software, books, movies, music, games. Banks and payment systems quickly joined the new trend, most of them have the tools to organize regular subscription payments. But the modules integrating the banking service with various sites often do not support this function yet. It turned out to be too expensive to develop such integration for all existing platforms.
To help you save time and money on developing the business logic of recurrent payments and integrate it into your website, we have developed the module "Regular payment and embedded recurrent payments".

Module functionality

The module automates receiving regular payments for products sold by subscription. When the buyer makes a purchase, a parent order is formed, according to which the first payment for the subscription takes place. In the future, the module monitors when the subscription period expires and creates a child order within the specified period, for which the next payment takes place.

The module works with both card payments and account payments.

In the first case, it automatically sends a payment request to the bank at the appointed time. If the required amount cannot be debited the first time, the module repeats the request several times. The request limit is specified in the module settings. If the money cannot be debited after that, the module automatically cancels both the child and the parent order and cancels the subscription.

In the second case, the module generates a child order a few days before the subscription expires, for example, 10 days in advance. After forming a child order, the module sends the buyer an email with a reminder that in a few days he will be billed for the next subscription period. Then, 5 days before the end of the subscription period, the module issues an invoice and sends it to the buyer. As soon as the buyer pays the bill, the module automatically renews the subscription. If the payment is not received, the subscription is canceled.

Our module contains the complete logic of recurrent payments, which can be integrated with any module of a bank or payment system. This will save time and money on developing the necessary functionality for each payment system used.

Module setup

First, you need to set up the payment methods that you will use on your website:

• Payment by card via bank,
• Payment via various payment systems,
• Payment by invoice.

Then you need to set up the mapping of order statuses to payment statuses. There are two possible work logics here: the order status depends on the payment status, or the payment status depends on the order status.

The first option is suitable for automatic payment methods: from a card or through payment systems. The module requests payment through the specified payment system, receives a response, automatically changes the payment status, and then the order status changes.

The second option is intended for payment by invoice. The module sends the invoice to the buyer, the manager tracks the receipt of the payment, manually changes the status of the order, the module automatically changes the payment status.

Decryption of statuses

The order has been created and is awaiting payment confirmation: the status is set to the order immediately after making the purchase and before the payment is received from the buyer.

Subscription extended (payment has been completed): after the child order receives the status "Paid", the status of the parent order changes to this one.

The request for a recurring payment was successful: the status for payment by card is set after successful debiting of money.

The bank rejected the operation: The automatic payment failed, the bank rejected the operation for any reason.

The subscription was canceled by the administrator: the administrator canceled the subscription, the buyer will not be able to renew it.

The subscription was canceled due to the expiration of the request limit: the module made the number of requests specified in the settings, but it was not possible to debit the money, the subscription was canceled.

The client has unsubscribed: the client canceled the subscription on his own, the money will not be debited. The client can renew the subscription at any time.  

Detailed instructions for working with the module