Can I present the PayPage terminal inside my browser-based applications user interface?
The preferred mechanism for browser-based applications is to use the transaction result redirect POST. When the transaction completes, PayPage will redirect to the url you have instructed the merchant to set along with POST data containing the transaction results. If the CustomerId and UserData fields were set during transaction ticket creation, they will be included in the redirect POST. You can use that information to restore the desired state of your browser-based application. If you wish for your merchants to feel like they are not leaving your application during the transaction processing stage, you can render the terminal within an IFRAME. Please note that the terminal page will not “talk” to the parent windows, so you will need to make use of the transaction result redirect, querying, or user action to determine when processing has completed.
- Will DonorNet users be able to correct validation errors through a user interface in the online application or must invalid data be corrected in the XML file and then re-uploaded to DonorNet?
- How do I license a Pegasus Imaging control on a server-side web application that does not provide a user interface?
- What is the default Seavus Project Viewer Graphical User Interface after installing and starting the application?
*Sadly, we had to bring back ads too. Hopefully more targeted.