Our company has decided to use Business Catalyst but we need help with an activation wizard for our product. This activation is also used to create a recurring monthly billing order.
We're thinking we need to use the API, here's our basic flow:
Customer Clicks Activation Button
Prompted to Login or Register
Customer looks up unit number (Can be called via a provider API)
Unit number is placed into field
Customer fills in billing information (or can it be pulled via BC API?)
Name
Address
Phone
Credit Card Info
Order is sent to BusinessCatalyst WebServices API to create recurring order
Billing Information is attached to Provider Database via API
Customer is forwarded to Subscription_thank_you page (url to be determined later)
Our team has never worked with the BC API and would like to know the best route to handle this scenario...should we embed the application in an iframe and put the iframe on a page in a secure zone or should we use the API to push user information from our BC site to an app residing on a subdomain? If anyone has experience with this type of situation or can point us to someone that has, please let me know, it would be greatly appreciated!
Thanks,
Andy
Hi Andy,
These API calls to the external app, such as "Customer looks up unit number (Can be called via a provider API)", can that be done with Javascript? You see, you can not run server side code on BC, so you have to resort to JS. If you can do it with JS I think that your requirement is possible.
You can check the API docs here http://kb.worldsecuresystems.com/635/bc_635.html and see the type of webservices we offer.
Cheers,
-mario
Ok, we have a solution in the works that includes javascript, but would like to know if we can pass custom arguments through the /FormProcessv2.aspx script.url so that we could invoke a different receipt - buy page based on url arguments. We would want to include two hidden field entries that we will be including in the form and will add them using a custom onclick event for the check out form submit button. This would allow the javascript planted on the receipt - buy page to know what path the buyer is coming from. We'll have buyers that are buying the normal route, simply adding items to their cart, but will also have people activating their device which includes purchasing a recurring product for which we will use javascript to automatically add to cart. The receipt - buy page will stay in the original form for all buyers simply adding items to their cart and purchasing, but will change when they are activating. The passed url arguments will tell our javascript which type of customer they are and will load the page accordingly. Will /FormProcessv2.aspx strip out our customer arguments and resort back to the default?
Thanks,
Andy
North America
Europe, Middle East and Africa
Asia Pacific