A reputation built on flexibility, scalability, and performance
Prelude was founded, and continues to be run, by engineers. As you might imagine, we measure ourselves not only by our clients’ satisfaction, but also by the excellence of our software.
Our flagship product, PayPilot, was designed with a multi-tiered client server architecture to scale with your company’s growth and to offer maximum flexibility to meet your unique—and evolving—payment processing needs.
View the System Architecture diagram below by clicking and holding your mouse on the orange slider at the bottom, and then moving it to the right. To view the diagram in a full-size, printable window, click here.
PayPilot draws its strength and flexibility from the heart of the system, its database. Our payment database provides centralized control with distributed access to all payment management functions. As a data-driven system, PayPilot can be completely configured to match—and automate—your business rules, your workflows, and your terminology.
We currently offer several database options including Microsoft SQL Server or Oracle. Our expertise extends across all options for database management, security, and retention of data for easy backup and recovery.
Seamless Integration, Automatic Operation
Our fluency with such a wide variety of systems and data types is a key differentiator for Prelude in the marketplace. PayPilot easily interfaces with any business systems (general ledger, claims, policy, accounts payable, etc.) in any industry setting. Data passes between systems using interfaces configured by our implementation team in the precise format you currently use: MS SQL or Oracle tables; ASCII flat files; XML; Excel spreadsheets; print image files; etc.
Once the interfaces are in place, many of the centralized payment functions can be run as a service on the application server, with no operator involvement. Our AutoPilot service can be configured to handle any number of jobs, freeing your staff from routine and repetitive tasks.
