Stripe already proved online card capture for many RPM PRO sites. Real portfolios still meet merchants, banks, and regions that prefer other rails. Supporting CardConnect alongside Stripe is not indecision—it is meeting guests and business constraints where they are, inside one property management software booking flow.
One booking experience, pluggable payment rails
Guests should not learn your processor name. They complete a booking payment page; the configured gateway handles capture, tokens, and failure messages. Admin UI for gateway settings must make the active path obvious so staff do not test the wrong mode in production during peak season.
Operational differences property managers must respect
- Settlement timing and statement descriptors differ by processor.
- Refunds and partial captures need gateway-specific handling.
- PCI scope depends on whether you host fields or redirect.
- Owner reporting should still show a unified “paid” story regardless of rail.
Choose deliberately, document clearly
Multi-gateway support fails when only one person knows which property uses which account. Keep gateway choice in settings, log payment attempts, and train staff on the refund path for each rail. If you are adding a second gateway, run parallel test bookings end to end—including failed cards—before the busy weekend.
Payments in RPM PRO
RPM PRO is property management software built for real booking and payment complexity—not demo-day happy paths. Explore RPM PRO property management software at https://www.rpm-pro.com/ — built for vacation rentals, long-term rentals, and mixed portfolios.
Operators evaluating a vacation rental payment gateway often need Stripe property management checkout and CardConnect (or similar rails) without splitting the guest booking experience. RPM PRO treats payment gateways as pluggable configuration with admin clarity—critical before peak season.
Ready to run LTR and vacation rentals in one system?
Explore RPM Pro features, pricing, or start a free trial—no credit card required.
