In-AppIn-app refers to services and features that are available from within a software application, usually in a mobile phone app. storefronts contain checkout processes, order processes, or other customer self-service features that open within an iframe in your software. They create less friction by allowing customers to check out, upgrade, or make purchases directly in the application, without the need to open a browser.
How to Integrate
Before we can set up an In-App checkout for your account, you must provide cleverbridge a list of the payment options that you want to offer in your In-App checkout. Contact Client Experience for support in choosing proven payment options.
The method for embedding the browser object in your application depends on the programming language you use. This can be implemented with almost every programming environment. For an example of how to embed the object in your application, see the In-Application Checkout Process: C# sample code.
To provide the best possible experience, you should make it possible for your customers to instantly activate the products that they purchase in your In-App checkout. To do so, use a special license key template that enables your application to find and parse the key on the confirmation pageThe confirmation page is displayed after a customer makes a purchase. The confirmation page contains the order confirmation and delivery information. after the order has been placed.
For the sample Tic-Tac-Toe application, we configured a key template that includes the key twice, as shown below in the Commerce Assistant’s Product portal in the Delivery Texts area:
The first key is an HTML comment for your application:
<!--LICENSEKEY=abc-123-def -->, which complies with your application’s search function. This format also ensures it does not display to the customer.
The second key is plain text for the customer’s use: Your license key:
abc-123-def. The customer can access the key from the confirmation email or for ordering the product directly in a web browser.
As a best practice, your application should search the HTML code in the embedded browser object regularly. This search should be conducted when a new page is loaded, or periodically, such as once every second.
The following examples illustrate the two formats in which you can configure this information. You can choose one of these two formats:
<!-- PURCHASEID=55033549--> <!-- LICENSEKEY=123-ABC-456-DEF--> <!-- ORDERTOTAL=99.95--> <!-- CURRENCY=EUR-->
<!-- [[purchaseId=55033550]] [[deliveryEmailfirstname.lastname@example.org]] -->
For a full list of the available license key template placeholders, see Define a License Key Template.
The following is an example of an In-App checkout process using the sample cleverbridge application Tic Tac Toe.
When a customer opens the sample application, Tic Tac Toe, a Buy now browser object appears at the bottom of the window.
When the customer clicks on the embedded browser object, he/she is directed to a customized cleverbridge order page. To accomplish this, the object opens a cleverbridge URL.
The customer fills in the Your details and Payment details pages.
This customer is directed to the Review your data page, and clicks BUY NOW.
The customer is told to wait while the order is processed.
After payment processing is complete, the application recognizes that a license key has been successfully issued for the customer. The key is automatically injected into the application for activation.
To download the Tic Tac Toe application, open in-application-checkout-process-example-app.zip.
To learn how to embed a browser object in your application, open In-Application Checkout Process: C# sample code.
The following is some additional information that you should consider when you decide to use the in-app integration method:
Just as our designers create checkout page layouts that match the styling of your existing website, our In-App designers apply the look and feel of your software application. However, the following characteristics can make it challenging to integrate in-application checkouts.
We recommend that you make the buying window as large as possible so that you can include marketing tools in the In-App browser.
In several In-App processes, scrolling is disabled by the software, and this can make it difficult to deal with the height of the content. If you want to implement In-App processes, we strongly recommend allowing scrolling within your application’s iframe.
If you use the Internet Explorer plugin that is installed on most Windows computers, make sure to use the latest rendering engine. If you don't, companies like PayPal may block your customers from paying.
When configuring the in-application checkout process for your application, you must have either a Review page or a Shopping Cart page for compliance reasons.