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 spread payments by currency, amount or a percentage split. Start with one and add more whenever you like — see Configuration.

What happens if a provider is down or misconfigured?

Routing selects only active, fully-configured providers:

• Fallback sequence: If primary routing rules find no match, RelyPay evaluates the configured fallback chain (set separately for INR and non-INR).
• Redundancy: Spreading checkouts across multiple providers eliminates single points of failure. See Routing.

Are customers ever blocked because of my license?

No. Customers can always pay. 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.

How are Indian (INR) and international payments handled?

Payments are partitioned by currency and jurisdiction:

• INR transactions: Evaluated by amount slab rules first, followed by percentage volume splits.
• International transactions: Evaluated by invoice currency first.
• Dedicated sub-gateways: Sub-gateways are tailored per region (e.g., UPI and Net Banking for domestic; Cards, PayPal, and Other for international). See 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.

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.

How is a recurring auto-charge capped?

Recurring charges are governed by two admin controls:

• SI Max Amount Multiplier: Capped at 1x–5x (default 3x) of the initial transaction amount.
• Days Before Due to Charge: Scheduled 1–5 days (default 2) prior to invoice due date. See Recurring payments.

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?

Updates are managed via Global Settings → Update Status:

• One-click process: Click Check for Updates, then Update Now.
• Automated safeguards: A full backup is captured beforehand; failed updates rollback automatically.
• Database snapshots: Retained snapshots can be downloaded from Database Backups. See Updating.

How do I show different payment methods to different customers?

Use 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?

RelyPay decouples client presentation from payment processing:

• Sub-gateway: The client-facing checkout method (e.g., UPI, Cards, Net Banking) enabled under Setup → Payment Gateways.
• Provider: The payment processor (e.g., Razorpay, Cashfree, PayGlocal) executing the transaction. See 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 rule may be hiding it for that customer. Check both. See Troubleshooting.

What are the server requirements?

PHP 8.2+, WHMCS 8.13+ or 9.x, a compatible ionCube Loader (13.0.2 or newer), SSL, and the curl, openssl, json, zip and mbstring PHP extensions. Full list on 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.

Where can I see every payment attempt?

In the transaction log (Addons → RelyPay → Transactions) — a searchable, CSV-exportable record of each attempt, the provider that handled it, the fee and the outcome.