Latest Activity...
Looking forward to this very soon! Thank you Ownerrez for actioning this!
[This topic has been merged with another topic (Approve Ownerrez direct integration with Powertranz- 3DS2 transactions). All unique votes have also been merged.]
[Another topic was closed as a duplicate of this topic (Payment Gateway Support for Costa Rica)]
The timeline isn't firm yet. This work moves from development over to our testing team very soon. What transpires during testing will ultimately determine how quickly we can roll it out.
I do not think we'll be needing to beta test this feature, but if that changes, we will certainly let users know!
Great news, Simon! 3DS support for Powertranz is already in active development. It's going to be moving to our testing team very soon.
That said, I'll mark this request In Dev. We'll post updates here as they become available.
Hi Ownerrez,
It would be great if we could get Powertranz/(First Atlantic Commerce) to have direct integrations with 3DS2 transactions. We have limited options in the Caribbean and Latin America for this integration with Payment processors, local banks and your system.
Increasingly the banks our now using 3DS2 feature to decrease risk of fraud and chargebacks.
Kind Regards
I already did create a support ticket for this.
When I received the support response from Emond de Weerd (pasted below), he suggested I submit a feature request... so that's what I've done : )
This feature is needed.
**********************************************************************
Hi Laura,
1. Advanced Matching: OwnerRez does not currently pass hashed customer information to the Meta Pixel during checkout. Our Pixel initialization is the standard fbq('init', '<your pixel ID>') call without an Advanced Matching object. There isn't a setting for this; the feature isn't implemented in our integration today.
2. Conversions API (server-side): We don't currently send events to Meta server-side via the Conversions API. The OwnerRez Meta integration is browser-Pixel only.
3. Purchase event payload: The Purchase event fires with value, currency, content_category ("OwnerRez Property"), content_name, content_type ("product"), and content_ids (a single ID identifying the booked property). It does not include customer matching data (email/phone/name), that ties into question 1.
Both Advanced Matching and the Conversions API would be great candidates to file as feature requests on our forum so other hosts can upvote them and our product team can gauge interest:
https://www.ownerrez.com/forums/requests
Kind regards,
-Emond
Need to support the following functionality:
Rental Agreement A for Property A needs to upload driver’s license and state number of guests staying at property
Rental Agreement B for Property A - needs upload of proof of vehicle insurance
Rental Agreement C for Property B - needs name of event, number of people attending event
Currently ALL guests staying at both property A and B regardless of rental agreement being presented to them for signing - see all custom fields. Based on example above they see:
driver’s license
number of guests staying at property
proof of vehicle insurance
name of event
number of people attending the event
It is confusing to guests as to why data that is not applicable to them should be entered.
Currently rental agreements are per property. This is good.
Custom fields definitions should be per property as well as per rental agreement.
Thanks for sharing this idea with the community! Feature requests with more support tend to move up our list faster, so if there's anyone else who'd want this too, point them to this thread and encourage an upvote.
Delighted to hear that you are adding support for 3DS for Powertranz. This is really great news. Is there an approximate time frame for availability? Is there going to be a beta or some other early release?
Appreciate you flagging this one! The upvote count at the top of the page is one of the biggest signals we use to decide what to build, so if this resonates with others you know, loop them in and have them add their vote.
Feature Request: An added function of Rezzy AI to Aggregate Guest Data Access for Guest Avatar Development
I'm submitting this as a formal feature request and hope fellow OwnerRez users will upvote it.
Right now, Rezzy cannot read or synthesize the data we've already built inside the platform. That's a significant missed opportunity. Here's what I'm asking for:
For clarity- What I want Rezzy to be able to do:
Why this matters:
If you've wanted the same thing, please upvote this request.
Hello!
You should be able to do this by enabling the Validate Inquiry option on the booking widgets. If this option is checked, guests are required to enter a guest count before they can submit an inquiry. To enable this option, go to Settings > Hosted Websites > click on the site name > click on the Book Now page under Menu and Pages > click Change Settings across from the Booking/Inquiry widget. In the pop-up, check the Validate Inquiry option and save the changes. Be sure to do this for the booking widget on the <property name> page as well if you're using a multi-property hosted website:
If you don't have a hosted website and are using just the widgets, the same thing can be done by going to Settings > Widgets > click into the booking/inquiry widget > click the Change button. It should have the same box to check, adn then save the changes.
Thanks for putting this feature request together! These ideas grow when more voices weigh in, so if you know other users who'd find this useful, send them the link and ask them to upvote. Community feedback really helps us prioritize what to build next.
In the meantime, for guests who cancel the same day they book, OwnerRez has a grace period that you can configure for cancellation policies that apply to direct and Vrbo bookings (if your Vrbo API is set to use your custom cancellation policy in OwnerRez). This only authorizes the payment, and doesn't collect right away to help tackle the issue of non-refundable credit card processing fees. We have this support article that goes over it and how to set it up: https://www.ownerrez.com/support/articles/cancellation-policies-overview#grace-period
Hey Laura!
Could you please submit a ticket to help@ownerrez.com about this so we can investigate?
We've received your feature request—thank you! If you think others would love this too, spread the word and invite them to upvote. Community feedback really helps us prioritize what to build next.
Hi Leon,
I'm happy to report that an update to our integration with Powertranz is already in development. We integrate with Powertranz now, but what we're adding is 3DS support to open the door to other regions where their supported banks require it. Costa Rica is one of those places!
Hello, I hope you are doing well.
I have a question regarding the fields to be filled out for the rental agreement. When running a test, I notice that the postal address and city are mandatory fields (see the attached screenshot); there is a small asterisk next to them.
I would like to make it so that only the country is a mandatory field, rather than the others.
How can I do this? Could you please outline the steps?
Thanks in advance.
Costa Rica is a major destination for STR yet there is no supported payment gateway for Costa Rica in OwnerRez. This makes running a direct booking website quite a challenge and greatly diminishes the value of an OwnerRez account.
We are using ONVO Pay and would like to see a direct integration with OwnerRez.
On the {BUFIXUP} form, the first screen's next button says 'Looks good, finish booking'. I would think this is confusing for a guest since they have already booked and it's more of a 'finish updating your profile or missing information.' Anyway to update the words on the button to say 'Looks good, complete my profile.' Or something similar?
Thanks!
I experience many occasions where I have to ask a guest for their card information multiple times for various reasons because it is only stored at the booking level. Those scenarios include for example;
* A guest would like to extend their stay in a different unit because their current unit doesn't have the extended nights available. Sometimes utilizing multiple units in order to extend their stay multiple nights.
* A guest is booking multiple units to accommodate other family members.
* A guest has multiple units booked and decides at a later date to use a different card to add an optional surcharge such as a pet fee for each unit for example.
That is disappointing. Is there any other way that we can connect OwnerRez to Inntopia? We really need to be on our Destination Marketing booking site.
I use OwnerRez security deposits but frequently collect them outside of OwnerRez via Zelle to avoid processing fees and chargeback risk.
Currently, when I receive a security deposit via Zelle and record the payment on the booking, OwnerRez treats it as an overpayment rather than a refundable security deposit. As a result, security deposit statuses are not updated and any triggers or workflows based on security deposit collection do not run.
It would be extremely helpful to have a way to manually mark a security deposit as received, similar to recording an offline payment. For example:
Security Deposits → Record Deposit Received
Amount: $325
Method: Zelle / ACH / Check / Cash
This action would:
Many direct-booking hosts collect refundable security deposits through Zelle, ACH, checks, or other offline methods, and currently there does not appear to be a way to tell OwnerRez that a security deposit has been received without processing it through a card transaction.
Thank you for considering this enhancement.
If we can have seasonal cancellation policies for Airbnb, why can't we do it on our own website?
[This topic has been merged with another topic (Horizontal Scrolling in Ribbon View). All unique votes have also been merged.]
[Another topic was closed as a duplicate of this topic (Side Scrolling on the ribbon)]
[This topic has been merged with another topic (CC/BCC for email templates). All unique votes have also been merged.]
[Another topic was closed as a duplicate of this topic (“cc” and “bcc” fields in emails)]
So glad to see this feature! I'd like to suggest the cancellation policies in the dropdown here (and anywhere else this dropdown appears) be reordered to be least to most strict.
So change to:
This will be more intuitive than the current order, which looks to be just alphabetical, and also aligns with the order these policies appear across Airbnb's documentation and when adjusting the policy anywhere throughout their app.
I am dealing with an issue regarding Rezzy schedules not working as they should. I tried the "Ask Rezzy" feature to ensure I wasn't missing something. Sure enough, it flagged it as likely a bug and instructed me to email support (which I already had). I wish in instances like this where Rezzy itself identifies a bug, that Rezzy could flag it for the engineers or open an internal ticket. It would sure help streamline things and make it possible for us to get quicker responses and resolutions.
Please add a way for us to Rezzy to open an internal ticket or flag bugs for the support/engineer team -- similar to how it can create tasks for us.
