Introduction

Rather than storing sensitive card information yourself, PaySubs safely hosts this data and manages subscription billing based on your configured schedule. This reduces your PCI DSS compliance burden and frees up your development team to focus on building your core product. Enjoy predictable revenue streams and streamlined customer management with PaySubs; effortlessly scale your subscription business without the headaches of complex payment processing.

Benefits of Using PaySubs

• No SSL certificate required — the hosted page is secure
• All card data is stored and tokenised by PayGate
• Easy to set up on your website
• PaySubs supports initial (once-off) payment + ongoing subscriptions
• Merchants can also manage subscriptions via the PayGate Back Office

Integration Flow

There are two main steps to integrating PaySubs:

1. Redirect the customer to PaySubs to complete the subscription setup
2. Receive the response back on your RETURN_URL to process the result

sequenceDiagram
    participant Merchant Website
    participant Customer
    participant PaySubs
    participant "Return URL"
    participant "PayGate DB"

    Customer->>Merchant Website: Selects subscription
    Merchant Website->>PaySubs: Redirect via HTML form POST
    PaySubs->>Customer: Hosted card input form
    PaySubs->>"PayGate DB": Create subscription
    PaySubs-->>"Return URL": Redirect with transaction result

All transaction data is posted to PaySubs via an HTML form with hidden fields. The response will return to your system via the URL provided.

Create the Subscription (Reference page)

Redirect to PaySubs

Method: POST

Endpoint:

https://www.paygate.co.za/paysubs/process.trans

Body Type: x-www-form-urlencoded (or HTML form)

Parameters (fields):

📘

Checksum Calculation: Use the exact order of fields as listed above. More on this in the Security & Hashing section.

Response handling

Handling the Response

Once the subscription process is complete, the user is redirected back to the RETURN_URL you provided.

PayGate appends a set of query parameters containing the result of the transaction. These include:

📘

You must validate the response checksum to ensure the payload has not been tampered with.

Subscription Frequency Codes

These frequency codes determine when subscription transactions are processed. Codes are included as the SUBS_FREQUENCY parameter when creating a PaySubs subscription request.

Each code defines a specific interval and date pattern for recurring charges.

📘

Be sure to select a code appropriate to your customer’s billing expectations and the length of your subscription agreement.

Weekly Schedules

Biweekly Schedules

3rd Weekly Schedules

Monthly Schedules

Every 2nd Month

Every 3rd Month