Return to Merchant

After a subscription request has been processed, the customer is redirected back to the merchant’s application using the RETURN_URL.

This redirect occurs in the customer’s browser after the payment or subscription setup step is completed. It allows you to display a confirmation or error message and guide the customer through the next steps in your subscription flow.


How the Return Works

A typical PaySubs flow includes the following steps:

  1. The customer initiates a subscription request

  2. The customer is redirected to the hosted payment or subscription page

  3. The subscription is processed

  4. The customer is redirected back to the merchant’s RETURN_URL

  5. The merchant displays a success or failure message


Important Considerations

⚠️

The return to merchant is client-initiated and should not be used for final transaction or subscription confirmation.

Because the redirect happens via the customer’s browser, the data received at the RETURN_URL may be incomplete or tampered with.

Always validate the final subscription status using one of the following methods:

  • Notify URL (server-to-server confirmation)

  • Query or status check endpoints


Using the Return Data

You can use the data returned to your RETURN_URL to:

  • Display a confirmation or error message to the customer

  • Show subscription details (e.g. reference or status)

  • Guide the user to the next step (e.g. dashboard, retry, or support)

However, this data should only be used for presentation purposes, not for backend processing or reconciliation.


Best Practice

For a reliable integration:

  • Use the RETURN_URL for customer experience only

  • Use the Notify or Query mechanisms for final validation

  • Update your internal systems only after server-side confirmation