Highly recommend! Great app and exceptional customer service
The response time was incredibly quick, and very patient in explaining the steps I needed to take. It’s clear that the team is highly skilled and dedicated to delivering top-notch customer service.
What stood out the most was their willingness to go above and beyond. They didn’t just resolve my concern but ensured I fully understood the solution and felt confident moving forward. This level of care and attention to detail is rare and truly appreciated.
Thank you, Binariver Ltd. Support Team—you’ve gained a loyal customer!
Jurisdiction specific components
Response from developer
Thank you for your feedback. We’ve tested the jurisdiction-specific component using “ZC” as an example, and it works as expected. The issue you’re experiencing may be due to an incomplete workflow during the creation process. Please follow these steps to ensure proper setup: 1. Select “Add subfile type.” The app will create a new subfile type below the existing “DL” subfile. 2. Navigate to the newly created subfile type. Tap the “Subfile Type” field and enter “ZC.” The field should turn green once you press “Enter,” indicating the new subfile is named “ZC.” 3. You now have a new subfile type called “ZC.” To create components for it, go to the “Actions” menu and select “Create jurisdiction-specific component.” A new component will be created, but it won’t be assigned to a subfile automatically. To avoid mistakes and ensure it’s explicitly under control, you must manually assign the subfile. 4. Scroll to the bottom of the components list, find the newly created component, and explicitly select “ZC” as its subfile. 5. In the text field to the right of “ZC,” enter a suffix (e.g., “A”), finalizing the component as “ZCA.” 6. To complete the setup, enter the content for your component in the text field next to the suffix (e.g., “BBB”). If after following these steps you still experience the issue, please send us a screenshot at support@binariver.com, and we will resolve it within hours. Let us know if you need further assistance!
It’s not free…
$100 yearly? 😂
Response from developer
The application allows users to input their data and generates a valid AAMVA PDF417 barcode, which has been rigorously tested and validated by a wide range of users in real-world scenarios. The ability to accurately validate user data and produce a compliant barcode is the app’s primary feature and is essential for its intended use. As these functions are integral to the app’s workflow, they are offered exclusively as part of the subscription. Due to the interconnected nature of these features, they cannot be split into separate free or paid options without compromising the overall functionality and reliability of the service.
Remove mandatory components?
Response from developer
With the latest update, we have introduced the option of deleting mandatory components with a simple swipe gesture.
Superb and well worth the investment
Response from developer
We greatly appreciate your feedback. Your input is important to our ongoing efforts to improve the app for the benefit of users and their businesses. We thank you for your observations!
Scan
Response from developer
Please send your request to our email address at support@binariver.com and include a brief description of the problem you are having. We will promptly send you detailed instructions with screenshots and comprehensive explanations.
Jurisdiction specific components
Response from developer
Thank you for sharing your experience with us. It looks like you are having a problem where despite using "ZC" as an example and entering the data, you keep getting the message "ID not provided" We are here to help you resolve this issue. After you create a new component for a specific jurisdiction, it is important to know that the component initially appears at the bottom of the list. To resolve the "ID not provided" message, we recommend that you scroll to this newly created component. There, use a selector at the beginning of the line to explicitly select the "ZC" subfile This ensures that the "ZC" data is selected correctly. Until this step is successfully completed, the system will maintain the warning "ID not provided". This warning message is to ensure the accuracy and reliability of your data, especially if you are working with multiple jurisdiction-specific components. If you need further guidance or encounter any problems during this process, please do not hesitate to contact us for assistance.
Missing major component
Response from developer
Thank you for your feedback! We have taken it into account and amended the description of the DBA component to make it more visible. It was already specified as the fourth element of the Mandatory components subset.
