➤ Product: OfficeRnD Flex
➤ Who: Admins with developer support
➤ Where: Admin Portal
➤ Availability: All Flex plans
A hosted payment gateway gets your members paying online even when your preferred provider isn't one of OfficeRnD's native payment integrations. Your development team connects the provider's API directly to OfficeRnD Flex, and once it's live, members see a 'Pay Now' button on their Billing page that redirects them to the provider's own payment page for outstanding invoices. This suits organizations already committed to a specific provider, or those needing a payment method our fully integrated gateways don't cover.
This article covers the setup requirements for a hosted payment gateway and the specific limitations you should weigh before choosing it over a fully integrated provider.
Set up a hosted payment gateway
To use a hosted payment gateway, you need:
One or more dedicated software developers.
Access to the payment gateway's API.
Once set up, members can pay outstanding invoices through a Pay Now button in the Member Portal.
What a hosted payment gateway can't do
The Hosted Payment Gateway handles only outstanding invoices. Before choosing it, review what it can't do.
What the hosted payment gateway supports:
Members pay outstanding invoices from the Billing page on the Member Portal by selecting Pay Now, which redirects them to an external payment page.
What the hosted payment gateway doesn't support:
Immediate booking payments. It can't process charges at the time of booking or during purchases in Growth Hub.
Purchase flows. If the system is set to generate and send an invoice automatically, it still does both, but it doesn't collect payment details or charge the customer. Learn more about Purchase Flows →
Saving payment details. Unlike fully integrated gateways, the Hosted Payment Gateway doesn't store customer payment information.
Recurring payments. Because payment details aren't saved, automated recurring charges aren't possible.
Examples of unsupported use cases:
Immediate charges for bookings when using edited purchase flows.
Direct payments for purchases made in Growth Hub.
For these scenarios, use a fully integrated gateway instead.