Vodia Networks utilizes Stripe as its payment processor for billing on its hosted PBX services, enabling both postpay and prepaid billing options for customers. This integration allows for seamless electronic transfers between a customer’s bank and Vodia, simplifying the payment process for users. By setting up various billing plans and assigning them to domains, administrators can effectively manage customer payments while ensuring sensitive payment information, such as credit card details, are securely handled through Stripe's infrastructure. This approach not only enhances billing efficiency but also strengthens data security and compliance with payment regulations.
How Stripe Payment Works. Stripe is a payment processor, which means it supports the electronic transfer of money from a customer’s bank (issuing bank) into a merchant’s bank (acquiring bank) as payment for goods or services bought with a credit card. Vodia uses Stripe for postpay or pre-pays on the Vodia hosted PBX. We will discuss how to set up your Stripe account with Vodia billing.
Setup up the billing plan
Navigate to the administrator, and click on “List” then Monthly Billing
Name your Plan.
Choose your Currency.
Create a Fix account along with a description and price for the plan.
For billing to work per domain, you’ll need to assign the newly created plan to a domain.
Navigate to your domain
Click on the
Scroll to Plan
Assign your new Plan and save
Adding a prepaid amount on the domain
Navigate to Settings —> General Settings
Scroll down to Billing Settings and credit for outbound calls and save
Stripe Billing
You’ll need to sign up with Stripe to acquire your Stripe API at https://stripe.com/. The API Keys will be used on the Vodia PBX billing section.
Adding your Stripe API Token
If you’re running the Vodia hosted edition. you can navigate to Monthly Billing under the administrator page. Navigate to Stripe settings.
Enter your Stripe public key and your Stripe secret Key under the Stripe Parameter. If you would like to send the monthly invoice manually, you can turn the feature on or off.
Adding the customer billing information
Navigate to your domain
Click on Advance
Choose Billing Settings
Enter the customer billing address (note: billing information will be sent to Stripe’s network)
Add the customer company card (note: all credit card information will not be saved on the Vodia PBX but sent to Stripe’s network)
Auto-Refill (here you can add an automatic charge for the customer)
Current account credit is added on the domain as shown above
Add a charge amount
Add a minimum account balance and save
If you have any questions, please send us an email, support@vodia.com.
Vodia’s cloud PBX system enhances the Do-Not-Disturb (DND) function for hotels, allowing guests to manage their privacy through buttons in the room or on the phone. The system syncs with PMS for seamless functionality, enabling hotel operators to manually override DND when guests struggle to disable it. For critical situations, like room service follow-ups, the system allows specific extensions to bypass DND, ensuring guests are reachable when needed. VIP guest management features, guest-to-guest call restrictions and automatic resets upon checkout ensure privacy, security, and convenience, improving the guest experience while maintaining operational efficiency.
As businesses increasingly adopt Wireless Local Area Networks (WLAN), understanding its impact on Voice over IP (VoIP) is essential. While WLAN offers flexibility and mobility, it can lead to call quality issues due to packet loss and bursts during access point switching. To combat these challenges, organizations can utilize robust codecs like OPUS which are designed to handle packet loss effectively and employ Session Border Controllers (SBCs) to enhance jitter buffers. By incorporating these solutions, companies can ensure a more reliable VoIP experience that meets the demands of modern workplaces, allowing seamless communication without interruptions.
In the late 1980s, prank calls were a common form of entertainment but often caused confusion, similar to today’s call forwarding glitches. Recently, a client migrating to a new PBX system experienced disruptions when users mistyped numbers for call forwarding. While user errors are common, there's a bigger concern: calls being misdirected to emergency numbers or costly lines, especially since many VoIP phones lack security features. Solutions include restricting call forwarding to internal numbers, blocking access or allowing only specific, pre-approved numbers. Ultimately, balancing control over settings is essential to prevent glitches while keeping systems user-friendly.
.svg)
