Depending where you are in your SaaS transaction journey, you may or may not have all the components required to run the transact flow end-to-end in your own solution. The emulator has built-in landing page and webhook implementations for you to use as an interim. The various scenarios a detailed below:
Note: If the emulator is hosted in an environment outside of "localhost" (For example, in an Azure App Service), the landing page url will need to be configured with the url of the host. Either IP address or fully qualified domain name will work as long as you can navigate to "{host-address}/landing.html" in a browser.
In this situation, the landing page configuration value is configured in the same way as Scenario 2!
If you have built a landing page, or are in the process of building and would like to test the resolve and activate API calls, the emulator can be configured to launch your landing page after an emulated purchase.
This configuration value can be set through the UI: Navigate to the emulator user interface, select config, set the Landing Page URL and click set.
Note: Changing the value through the use interface will only persist the new value for the duration of the session. If the emulator is restarted, this value will be lost and will need to be reconfigured.
To make this value persistent across restarts, set the environment variable LANDING_PAGE_URL instead.
This configuration value can be set through the UI: Navigate to the emulator user interface, select config, set the Webhook URL and click set.
Note: Changing the value through the use interface will only persist the new value for the duration of the session. If the emulator is restarted, this value will be lost and will need to be reconfigured.
To make this value persistent across restarts, set the environment variable WEBHOOK_URL instead.