PaymentNg Overview for Customers
PaymentNg — Secure Payment Processing for Your Guests
What Is PaymentNg?
PaymentNg is a security improvement included in your RDP property management software. It affects the payment step inside the Internet Reservations Module (IRM), Owner Portal, and Self Check-In applications.
From your guests' perspective, the payment experience looks the same as before. Behind the scenes, the payment page now runs in a fully isolated environment — completely separated from any marketing and analytics tools running on the rest of your site.
Why Was This Change Made?
Many properties use Google Tag Manager (GTM) to run marketing tools such as Google Analytics, Facebook Pixel, and advertising conversion tracking. These tools are valuable for understanding your booking funnel and measuring the return on your marketing spend.
However, running third-party marketing scripts on the same page as a payment form introduces risk. Security researchers have documented ways that a misconfigured or compromised marketing tag can interfere with a payment page — including techniques that can intercept card data before it reaches your payment processor.
PaymentNg eliminates this risk by ensuring that no marketing or analytics scripts are present on the page where your guests enter their payment information. The payment form runs on a clean, isolated page that contains only what is needed to collect payment securely.
What Changes for Your Guests?
Very little.
-
The payment form looks the same.
-
The address bar will briefly show /paymentng/ during the payment step, then return to your booking site once payment is confirmed.
-
Most guests will not notice the transition.
Does This Break My Google Analytics or Conversion Tracking?
No. Your booking conversion events fire on the confirmation page, which loads after payment is complete. GTM and all of your marketing tools are running normally on the confirmation page — your conversion data is not affected.
The only page removed from GTM tracking is the card entry screen itself.
Which Payment Processors Are Supported?
PaymentNg works automatically with all RDP-supported payment gateways:
| Processor | Status |
|---|---|
|
RDPPay |
✅ Supported |
|
Shift4 |
✅ Supported |
|
Tenerum |
✅ Supported |
Your existing gateway configuration is used automatically. No additional setup is required.
Which Applications Are Updated?
| Application | What is Covered |
|---|---|
|
Internet Reservation Manager |
Online reservation deposits and additional payments |
|
Owner Portal (coming soon) |
Owner payments, reservation deposits, and points purchases |
|
Check-In (coming soon) |
Self check-in and self check-out payments |
Frequently Asked Questions
Q: Do I need to do anything to enable this? A: No. PaymentNg is enabled automatically as part of your software update. There is nothing to configure.
Q: Can I turn it off and keep the old payment page? A: No. The previous in-app payment screens have been replaced by PaymentNg. This is a permanent security improvement, not an optional feature.
Q: What if my guest takes a long time on the payment screen? A: The payment session is valid for 20 minutes. If a guest leaves the payment screen open and returns after 20 minutes, they will need to restart their booking. This is consistent with standard session timeout behavior and is part of the security design.
Q: Is this a PCI compliance requirement? A: PaymentNg reduces the scope of third-party script exposure on your payment page, which is aligned with PCI DSS best practices. For formal compliance guidance specific to your property, please consult your Qualified Security Assessor (QSA). RDP does not provide PCI certification advice.
Q: Who do I contact if guests report an issue at the payment step? A: Contact RDP Support as you normally would. Support staff have access to detailed transaction logs and can assist with any payment-related issue.
For questions about this update, please contact your RDP account representative or support team.