---
url: /relypay-whmcs/faq.md
description: >-
  Answers to the questions WHMCS operators ask most about RelyPay — using one
  provider or several, provider outages, licensing and customers, INR vs
  international, SSL, recurring caps, card data, updates and per-customer
  methods.
---

# FAQ

Short answers to the questions that come up most. Follow the links for the full detail.

## Can I use just one provider, or do I need several?

Either. Connect a single provider and every payment routes to it, or connect several and
let [routing](/relypay-whmcs/features/routing) spread payments by currency, amount or a
percentage split. Start with one and add more whenever you like — see
[Configuration](/relypay-whmcs/configuration).

## What happens if a provider is down or misconfigured?

Routing only picks a provider that is enabled and fully configured. If nothing matches, the
**fallback** chain takes over — set separately for INR and non-INR — using the first working
provider in the chain. Spreading payments across providers is exactly how you avoid a single
point of failure at checkout. See [Routing](/relypay-whmcs/features/routing).

## Are customers ever blocked because of my license?

No. Customers can always pay. [Allocations](/relypay-whmcs/features/allocations)
only control which methods are *visible*; if the license cannot be confirmed for an extended
period, the visibility filter simply stops applying and all gateways show. See
[Licensing](/relypay-whmcs/licensing).

## How are Indian (INR) and international payments handled?

INR payments route by amount slab and then by volume split; non-INR payments route by
currency first. Each has its own fallback. The sub-gateways are scoped too — INR methods
like UPI and Net Banking versus international Cards, PayPal and Other. See
[Sub-gateways](/relypay-whmcs/features/sub-gateways).

## Do I need SSL?

Yes. A valid SSL certificate is required — provider webhooks only deliver to a secure HTTPS
endpoint, and every provider API call enforces certificate verification. See
[Requirements](/relypay-whmcs/requirements).

## Which providers support recurring charges?

Recurring runs through **PayGlocal Standing Instructions** on international card
transactions. The **Recurring Payment Gateway** list only shows providers that support
international cards plus SI. See [Recurring payments](/relypay-whmcs/features/recurring-mandates).

## How is a recurring auto-charge capped?

By the **SI Max Amount Multiplier** (1x–5x, default 3x): any future auto-charge is capped at
that multiple of the first invoice amount. You also choose how many days before the due date
the charge is attempted (1–5, default 2). See
[Recurring payments](/relypay-whmcs/features/recurring-mandates).

## Is card data stored on my server?

No. Payments are handled by the provider's own checkout, and RelyPay records the outcome and
transaction reference — not raw card data. Provider credentials are encrypted at rest, and
every callback is cryptographically signature-verified.

## How do updates and backups work?

Update in one click from **Global Settings → Update Status**: **Check for Updates**, then
**Update Now**. A full backup is taken before every update; if an update fails, RelyPay
automatically restores both files and database. Recent database snapshots are listed under
**Update Status → Database Backups**. See [Updating](/relypay-whmcs/updating).

## How do I show different payment methods to different customers?

Use [Allocations](/relypay-whmcs/features/allocations) (**Addons → RelyPay →
Allocation**). Build rules by Country, Client Group, Product Group, Config Option Group,
Product Addon or Product Bundle, and list the sub-gateways each rule keeps visible. If no
rule matches, all sub-gateways are visible.

## What is the difference between a sub-gateway and a provider?

A **sub-gateway** is what the customer sees at checkout — UPI, Cards, Net Banking and so on,
each a real WHMCS gateway you enable under **Setup → Payment Gateways**. A **provider** is
the integration that actually takes the payment. RelyPay matches the two per transaction. See
[Sub-gateways](/relypay-whmcs/features/sub-gateways).

## Why isn't a payment method showing at checkout?

The method's sub-gateway must be activated under **Setup → Payment Gateways**, and an
[Allocation](/relypay-whmcs/features/allocations) rule may be hiding it for that
customer. Check both. See [Troubleshooting](/relypay-whmcs/troubleshooting).

## What are the server requirements?

PHP 8.2+, WHMCS 8.13+ or 9.0, a compatible ionCube Loader (13.0.2 or newer), SSL, and the
`curl`, `openssl`, `json`, `zip` and `mbstring` PHP extensions. Full list on
[Requirements](/relypay-whmcs/requirements).

## What happens to my data if I deactivate RelyPay?

Deactivating removes the generated sub-gateway files but **keeps your database tables**, so
transaction history and configuration survive a deactivate/reactivate. Removing the data
entirely is a separate, irreversible step. See [Uninstalling](/relypay-whmcs/uninstalling).

## Where can I see every payment attempt?

In the [transaction log](/relypay-whmcs/features/transactions) (**Addons → RelyPay →
Transactions**) — a searchable, CSV-exportable record of each attempt, the provider that
handled it, the fee and the outcome.