Payment processors
Active Reach charges customers via payment gateways (PGs) for one-time orders, membership subscriptions, and reward redemptions. You configure which gateways your workspace uses; the platform handles routing, fallbacks, and webhook processing.
Go to /dashboard/[workspaceSlug]/settings → Payments to manage.
Supported gateways
| Gateway | Best for | One-time | Subscriptions | Split payments |
|---|---|---|---|---|
| Cashfree | India primary | ✅ | ✅ | ✅ (Easy Split) |
| PayU | India fallback | ✅ | ✅ | – |
| Razorpay | India fallback | ✅ | ✅ | – |
| Stripe | International | ✅ | ✅ | – |
| PhonePe | India UPI-first | ✅ | – | – |
Workspaces in India default to Cashfree primary, PayU fallback, Razorpay fallback. International workspaces default to Stripe primary.
How routing works
Each payment attempt walks the priority list top-to-bottom:
- Try the primary gateway
- If the primary returns a routable failure (network error, gateway downtime, but not a card decline), try the next
- Stop at the first success — or surface the last error if all fail
You see the routing order at Settings → Payments → Priority. Drag to reorder.
Card declines are not routable — a declined card on Cashfree won’t retry on PayU. Only gateway-side failures (unreachable, 5xx, sandbox down) trigger fallback.
Connecting a gateway
Pick the gateway
In Settings → Payments, click Connect next to one of the supported gateways.
OAuth or API keys
Cashfree, PayU, and Razorpay all support API-key-based connection (simplest). Cashfree additionally supports OAuth for managed-mode tenants — recommended because tokens auto-refresh.
| Field | Where to get it |
|---|---|
| App ID / Client ID | The gateway’s merchant dashboard |
| Secret / Client Secret | Same dashboard, never committed anywhere |
| Webhook secret | Generated on Active Reach’s side and copied into the gateway’s webhook config |
| Mode | Sandbox vs Production |
For Cashfree, see the developer integration page for the full credential set including the secondary webhook secret used for abandoned-checkout events.
Verify
Click Test connection. Active Reach creates a sandbox order, simulates a webhook callback, and shows green if every leg works. Failures are itemised — typically a webhook URL mismatch or a wrong secret.
Enable
Toggle Live to start routing real charges through this gateway. New connections enter the priority list at the bottom; promote to primary via drag-reorder.
Easy Split (Cashfree only)
Cashfree’s Easy Split splits a single customer charge across multiple receiving bank accounts — useful for marketplaces, multi-outlet brands, and affiliate payouts.
When enabled, every charge is automatically split based on a rule set you configure at Settings → Payments → Split rules:
| Rule type | Example |
|---|---|
| Fixed % | 95% to outlet, 5% to platform |
| Fixed amount | ₹50 platform fee, balance to outlet |
| Dynamic per-order | Computed from order metadata (e.g. multiple outlets in one cart) |
Active Reach handles vendor onboarding (KYC, bank account, business type) through the same surface. See Cashfree integration → Vendor onboarding for the operator + developer workflow.
Subscriptions
For memberships and other recurring charges, the gateway must support subscriptions. Cashfree, PayU, Razorpay, and Stripe all do.
Active Reach handles:
- Plan creation in the gateway
- Mandate setup (UPI AutoPay / NACH / card-on-file)
- Renewal attempts and dunning retries
- Cancellation propagation back to the gateway
- Refund handling
See paid memberships → trial expiry for the dunning behaviour.
Refunds
Refunds are initiated from:
- Order detail page — full or partial refund
- Membership cancellation — automatic pro-rated refund if your policy is “immediate cancel”
- Bulk operations — admin-only, requires audit-log reason
Refunds always go back to the original gateway. The refund ID is preserved end-to-end so reconciliation matches.
Reconciliation
A nightly job pulls settlement reports from each connected gateway and reconciles them against Active Reach’s order records. Mismatches are surfaced at /dashboard/[workspaceSlug]/payments → Reconciliation:
- Charged but not settled — order succeeded on the gateway, settlement pending
- Settled but not charged — gateway sent money you don’t have a record for
- Refund mismatch — refund processed gateway-side but not reflected in Active Reach (or vice versa)
What’s next
- Cashfree developer integration — webhooks, signatures, vendor onboarding
- Paid memberships — subscription billing for loyalty
- Billing & credits — your own Active Reach subscription