Gateways
Connect Sandbox, Razorpay, Stripe, PayPal, PhonePe, Paytm, Cashfree or PayU with your own credentials, test the connection and set up the gateway's webhook.
A gateway is your own account with a payment provider. Money goes from the buyer to that account; REM Payments only records what the provider reports. Open Gateways to see each gateway with its mode (test or live) and health.
Connect a gateway
Choose Connect Gateway (or Create > Gateway).
Pick the provider: Sandbox, Razorpay, Stripe, PhonePe, Paytm, Cashfree, PayU or PayPal.
Enter the credentials from the provider's dashboard (for example Razorpay's key id and key secret, Stripe's secret key). Sandbox needs none.
Choose test or live mode, the currencies and the buyer countries it serves, and whether it handles subscriptions.
Use Test to check the credentials against the provider.
Copy the webhook address shown on the gateway page into the provider's dashboard, and enable the events listed beside it. The address looks like
https://rempayments.com/api/webhooks/razorpay/3. Test and live gateways have different addresses.
Secrets are encrypted and never shown again: the page shows them masked with the last four characters. Saving the form with the masked value keeps the secret; clearing the field removes it.
Which gateway a checkout uses
When a buyer starts a checkout, REM Payments picks the first gateway that is enabled and fits: it accepts the currency, it serves the buyer's country (or every country), and it handles subscriptions if the plan is recurring. The Default Gateway is tried first. An app can also route by currency (for example INR to Razorpay, everything else to Stripe). The hosted page lists every gateway that fits, so the buyer can switch.
Gateway page
Overview: mode, currencies, countries, payment methods, last webhook received and the last webhook error.
Gateway Calls: every request REM Payments made to the provider, with the answer (secrets and card numbers masked). Use it when a checkout fails to open.
Webhooks: what the provider sent, with status (processed, ignored, duplicate, invalid, failed).
When webhooks fail
An invalid inbound event almost always means the webhook secret on the gateway does not match the provider's. Correct it on the gateway page, then open the event under Webhooks > Inbound and Replay it: the stored request is checked again and applied.
Last updated 18 Nov 2026