Recurring Billing APIs are the simplest way to start collecting your monthly or yearly subscription fees automatically.

This API integration includes 4 Steps

Step 1 - Create a subscription plan

A subscription plan consists of basic information like plan name, amount, and frequency. An example of a subscription plan could be “Spotify Premium” which is SGD 9.90 monthly.

HTTP Request


Query Parameters

Mandatory fields are name, cycle and amount. Remember to include header Content-Type: application/x-www-form-urlencoded

namePlan nameSpotify Premium
descriptionThe description of the subscription planSpotify Monthly Subscription
cycleBilling frequency (weekly / monthly / yearly / custom / save_card). If cycle = custom then the user has to send the fields cycle_repeat and cycle_frequencymonthly
cycle_repeat[This field is only applicable when cycle = custom] It’s the number of times the cycle will repeat.4
cycle_frequency[This field is only applicable when cycle = custom] It’s the frequency of the cycle [day / week / month / year]week
currencyCurrency related to the recurring billingSGD
amountAmount related to the recurring billing9.90
referenceArbitrary reference number that you can map to your internal reference number. This value cannot be edited by the customerXXXX123
curl --location --request POST '' \
--header 'X-BUSINESS-API-KEY: meowmeowmeow' \
--header 'X-Requested-With: XMLHttpRequest' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'name=Spotify Premium' \
--data-urlencode 'description=Spotify Monthly Subscription' \
--data-urlencode 'currency=SGD' \
--data-urlencode 'amount=9.90' \
--data-urlencode 'cycle=monthly' \
--data-urlencode 'reference=spotify_premium_2022'


    "id": "973ee344-6737-4897-9929-edbc9d7bf433",
    "name": "Spotify Premium",
    "description": "Spotify Monthly Subscription",
    "cycle": "monthly",
    "cycle_repeat": null,
    "cycle_frequency": null,
    "currency": "sgd",
    "amount": 9.90,
    "reference": "spotify_premium_2022",
    "created_at": "2022-09-12T14:19:26",
    "updated_at": "2022-09-12T14:19:26"

Step 2 - Create a recurring billing for the customer

Once your customer has decided to start the subscription this endpoint will create the recurring billing request.
Since this is a server-to-server communication, if you have a mobile or Web client that communicates with your REST API, you must have a new endpoint E.g. /create-subscription or reuse an existing endpoint. This endpoint will be responsible for making the recurring billing API call to hitpay.

HTTP Request


Query Parameters

Mandatory fields are plan_id, customer_email, and start_date. If you would like to create a subscription without a plan, you need to send plan_id = null and the following mandatory fields: name, cycle, amount, customer_email, and start_date. Remember to include the header Content-Type: application/x-www-form-urlencoded.

plan_idSubscription plan id created from step 1973ee344-6737-4897-9929-edbc9d7bf433
customer_nameCustomer namePaul
start_dateBilling start date (YYYY-MM-DD) in SGT2022-11-11
amountBy default, the amount from the subscription plan will be used. Use this parameter for discounts for customers.7.90
currencyCurrency related to the recurring billingSGD
payment_methods[]Choice of payment methods you want to offer the customergiro, card
redirect_urlURL where hitpay redirects the user after the user enters card details and the subscription is active.
referenceArbitrary reference number for mapping purposes. Customer cannot edit this value.XXXX123
webhookOptional URL for hitpay to send a POST request on new charges or charging errors.
send_emailHitpay sends email receipts to the customer. Default value is false.true
times_to_be_chargedNumber of times to charge the customer.3

Step 3 - Redirect customer to recurring billing page (One time set up)

Redirect the customer to the “url” value.

Recurring Billing API UI

Once the customer completes the payment information it will be redirect to “redirect_url”

Step 4: Handle Successful Payment


HitPay will send a Webhook POST request when there is a new charge or if there is an error charging the card.
If you are using HitPay APIs to integrate into your app you must mark your order as paid ONLY after the webhook is received and validated.

  1. Create an endpoint (E.g. /payment-confirmation/webhook) in your server that accepts POST requests. This request is application/x-www-form-urlencoded.
  2. Validate the webhook data using your salt value
  3. Return HTTP status code 200 to Hitpay
  4. Mark your order as paid
sample webhook payload data

Webhook fields

Following fields are sent with the webhook request:

payment_idPayment ID
recurring_billing_idRecurring billing request ID
amountAmount related to the recurring billing
currencyCurrency related to the recurring billing
statusPayment status (succeeded / failed)
referenceArbitrary reference number that you have mapped during recurring billing request creation
hmacMessage Authentication code of this webhook request

Validate Webhook

Hitpay creates a list of all values from the key-value pairs that we send in the POST request and sort them in the order of their keys alphabetically. We then concatenate all these values together. We then use the HMAC-SHA256 algorithm to generate the signature. The HMAC key for the signature generation is the secret salt from your dashboard under Settings > Payment Gateway > API Keys.

public function generateSignatureArray($secret, array $args) 
        $hmacSource = [];        

        foreach ($args as $key => $val) {
            $hmacSource[$key] = "{$key}{$val}";


        $sig            = implode("", array_values($hmacSource));
        $calculatedHmac = hash_hmac('sha256', $sig, $secret); 

        return $calculatedHmac;

Congrats! You have now successfully completed the recurring billing integration.