Integrations
What it connects to
An agency's work does not end inside one system: invoices go to an integrator, messages to an operator, rates to the central bank. Every connection sits behind a provider interface — changing a provider does not change the module.
In older software most of these connections worked like this: the program opened the other site's page, filled the fields itself and pressed save. The day that site changed its layout the connection stopped working, and staff went back to typing by hand until someone fixed it. Here each outside service sits in its own compartment: changing your e-invoice provider does not disturb the rest of the program, only that compartment changes.
Financial
İzibiz e-Invoice
WorkingFinancial
Issuing invoices, pulling incoming ones, accepting or rejecting commercial invoices and querying status. The integrator seals the response document, so there is no certificate to carry.
e-Archive
WorkingFinancial
The document issued to a passenger who is not an e-invoice taxpayer. Same integrator, same screen.
Central bank exchange rates
WorkingFinancial
Rates are pulled automatically each business day, buying and selling separately. The rate at the time of the transaction is written onto the movement and never recalculated.
Payment gateway
PlannedFinancial
Letting a passenger pay an instalment from their own page. Collections and ledger are ready; the gateway connection is planned.
Communication
SMS delivery
WorkingCommunication
Payment reminders, departure notices and bulk announcements. Delivery runs on a queue, so a hundred-recipient send does not block the screen.
Communication
Sending links and reminders to passengers. Because it needs template approval and number verification, setup is done per agency.
Infrastructure
S3-compatible storage
WorkingInfrastructure
Passport scans, photographs and contracts. Files are handed out through signed, expiring addresses rather than served directly.
Hardware
Passport and ID readers
WorkingHardware
Data from an MRZ reader lands on the passenger card. Readers in keyboard mode need no extra software; chip readers need a small local bridge.
Official
Nusuk Masar
WorkingOfficial
Saudi Arabia consolidated the old Umrah portals under Nusuk; there is no public API for agencies. Submission runs through a desktop helper opened with the agency's own Nusuk account: passenger data is filled into the form automatically, only the captcha is done by hand.
Diyanet
In progressOfficial
Reporting Hajj and Umrah registrations to the Diyanet portal. Passenger and photo submission also runs through the same desktop helper; this module is being added.
All questions
Can we use our own e-invoice integrator?
On the Enterprise plan, yes. Invoice generation sits behind an integrator-independent interface; adding one means writing that interface's implementation, not touching the module.
Do we have to buy SMS credits from you?
No. You enter your own provider's credentials in settings and messages go out on your account. The credentials are stored encrypted.
How does Nusuk submission work?
The Saudi side offers agencies no public API, so submission runs through a desktop helper that drives the portal with the agency's own account. Passenger data is pulled from the system and filled into the form automatically; steps that need a human, like the captcha, stay with the operator. The result — the application/MOFA number — is written back to the passenger.
Are the legacy browser-automation integrations being carried over?
The code isn't, but the method is in the same family: with no official API, submission still runs through a desktop program that drives the portal. The difference is that it's rewritten from scratch — each portal in its own compartment, on the agency's own account; when a portal's design changes, only that compartment is updated and the rest keeps running.
Let's set it up together
Tell us how your tours, pricing and team are structured; we will show the demo on a setup that resembles your own data.