It should fit the tools
you already pay for.
NiroStay is the record. Other services do one job well — take the card, carry the rate, deliver the email. Here is every connection that exists today, what it needs from you, and the ones still being proven.
The guest pays once, and it is provable.
NiroStay never holds a card number. The gateway does what it is licensed to do, and the console records only what it can prove.
Cards, transfers, USSD
Your own merchant account, connected in Settings. Use it for a deposit at booking or the full stay. The guest is handed to Paystack's checkout and returned with a reference, never with card details in our database.
You need: a Paystack account and its secret key.
LiveRecorded at the desk
A transfer is recorded against its reference, with who took it and when. It moves the balance immediately, but it is labelled as recorded rather than verified — the distinction matters when a guest says they paid.
You need: nothing beyond the console.
LiveSigned, deduped, apply once
A gateway callback is signature-checked and stored before it is acted on. A provider retry is acknowledged, not applied twice, so a flaky connection cannot double a payment.
You need: a reachable deployment, which we set up with you.
LiveProvider statement against the book
Import a settlement statement and every line is matched to a charge, a fee or a refund. A line that does not match stays visible as needing a look instead of disappearing into a total.
You need: the statement file from your provider.
LiveYour own front door first.
A direct booking is tracked as its own channel. OTA connections go through one adapter rather than a different integration for every site.
Search, hold, confirm
Served at your organisation's own address, painted with your name and colours. Availability comes from the same inventory as the front desk, so the site cannot sell a room the desk has taken.
You need: nothing — it is part of every plan.
LiveThe channel adapter
Provider-neutral mappings, a durable inbox for rate and booking messages, and a coalescing outbox for availability. Built and tested against a stub provider; live accounts are connected property by property.
You need: a Channex account, or a conversation with us about onboarding.
ConnectingThrough the adapter, not around it
These are reachable through Channex. We will not claim a live connection we have not run with a property, so the status below is the honest one until each connection has been proven in production.
Connectinglekkiprime.com, not a subdomain
On Portfolio, add one DNS record we give you. We verify it, serve the booking page there and keep the certificate in order. The address root answers with the site you nominate.
You need: access to your domain's DNS.
LiveQuestions become threads
A guest question from the site lands in the console with the stay it is about. A reply is emailed from your property's identity and kept in the thread, so the next shift can read what was promised.
LiveHand-off, with consent
A guest who ticked WhatsApp gets a click-to-chat hand-off from the thread. The message opens in your own WhatsApp; there is no unofficial automation and no borrowed number.
LiveThe guest should see your name, not ours.
Confirmations, receipts and enquiry replies are painted from the property's own identity. The provider is a delivery route, not a brand on the page.
Transactional email
One API key and a verified sending domain. Every message is logged with the provider's verdict, so a failed receipt is visible rather than assumed delivered.
You need: a Resend account and DNS for the sending domain.
LiveThe other provider
The same templates and the same delivery log, for operators or deployments already standardised on Postmark. Switching provider is a configuration change, not a rewrite.
You need: a Postmark server token.
LiveNothing sent by accident in dev
In development every message is captured and readable in Settings instead of being delivered. It is how the invitation and reset flows are tested without a real inbox.
LiveNot yet
Nigerian guests often prefer a text. It is on the roadmap and not on the price list; until then, WhatsApp hand-off or email covers the same message.
NextYour book, in a form you can take with you.
Export is a feature, not a favour. Nothing about leaving requires a support ticket or a negotiation.
Reservations, guests, folios, reports
The same figures the console shows, as a file a spreadsheet or an accountant can open. Export is scoped to your organisation and your role.
LiveVersioned and tenanted
Routes under /api/v1, scoped by organisation and role, with consistent errors and correlation ids. Portfolio plans include access; earlier plans can ask.
Receipts, invoices, credit notes
Printable receipts and issued tax documents with numbers from your own sequence. A credit note corrects a document; nothing is deleted to make a total agree.
PilotNo direct sync yet
There is no QuickBooks or Xero connector. The export is the bridge today, and a direct sync is deliberately not promised before it is built.
NextThe list is short on purpose.
Every integration is something that can break at 9pm on a Friday. We add one when an operator needs it, not to fill a logo wall.
- No door-lock hardware. Key cards and smart locks are not integrated. The unit, the guest and the folio are; the physical key is still yours.
- No restaurant POS. Extras can be posted to a folio, but a restaurant's own point-of-sale is a different product with a different day.
- No marketplace ambition. We do not want to own the guest relationship or sell your rooms as our inventory.
- No native mobile app yet. The console is responsive and housekeeping is touch-first; a native shell is on the roadmap, not in the App Store.
- No live OTA marketplace. Booking.com and Airbnb arrive through a channel manager, not through a direct partnership we have invented.
- No silent automation. We will not read a guest's WhatsApp for you or send messages from an unofficial number.
What operators ask before connecting anything.
Do we need to change our payment provider?
No. If you already use Paystack, connect the merchant account you have. If you take transfers, keep taking them — the console records them with a reference and shows the difference between recorded and verified money.
Who pays the gateway fees?
You do, directly, at your provider's rate. NiroStay does not mark up processing or take a spread. That is why the subscription is the only line on our invoice.
Can we keep our current email domain?
Yes, and you should. Guest mail is sent from your verified domain through Resend or Postmark, with your property's name on it. The provider is infrastructure, not the sender the guest sees.
How long does a channel connection take?
It depends on the OTA and the property's mapping. We set up the adapter, map unit types and rates, and run a test booking before switching a channel on. We would rather take a week than promise a switch we have not tested.
Can we get our data out if we leave?
Yes. Reservations, guests, folios and reports export as CSV, and the terms include a 30-day export window after termination. Leaving is a download, not a support ticket.
Bring the stack you already have.
Tell us what takes your money, what carries your rates and what sends your email. We will say what connects today and what would still be manual.
Prefer to read first? The full FAQ is here.