In-app is a intuitive pop up style checkout. On clicking the Subscribe/Checkout button, a pop up would open where your customers will have to enter their account and payment details. You can choose to configure your brand elements, fields, display charges, taxes, a thank you message and play around with multiple workflows to suit your business needs!
Here is a sample of the In-app Checkout.
Users signing up from Feb 06, 2018 will have In-app checkout enabled by default. In case you are using the single page Checkout and wish to try In-app checkout, please watch the below video.
This is applicable only in Test Site. Please contact [email protected] to enable it in the Live Site.
Before you configure In-app checkout, please make sure that you:
As a merchant, depending on your business model, you can choose how you'd like to set up the Checkout. Chargebee provides you with three options to choose from.
Drop in Script is an easy to use plug-in modal that requires zero developer help. You can easily create a checkout page by adding a script generated for the plan in your HTML page.
Checkout pages generated using drop in script are Level 1 PCI compliant and all that you have to do is fill in this questionnaire.
To use the drop in script to create checkout pages:
Here is a sample checkout.
In case you would like to have a separate URL for your checkout rather than using the In-app, you have 2 options:
Use the single page checkout (Read more about this here.)
Create a plan specific URL: When you use this option, the user interface of the In-app checkout gets retained but, the checkout screen will open as a new URL rather than a pop up.
Here is the syntax to create a plan specific URL:
Replace the site name and plan ID with your site name and plan ID. For example if my site name is ‘docstest-test' and my plan ID is 'sapphire' then this is how my URL would look like
This is particularly useful if you are using a website that does not allow you to add scripts.
Checkout via API is extremely useful when you want to have a user management or authentication system at your end.
Here is a quick example when you'd want to choose Checkout via API instead of Drop in script.
Let us assume that James runs a digital weight loss and fitness app. He wants to collect user information such as the client's height, weight, food habits etc along with his address, email and store it in his database instead of Chargebee. But, he would still like to use Chargebee's checkout as he does not want to get involved in the nitty-gritty details of PCI Compliance.
James can choose the API integration as this would allow him to collect partial information at his end and then use Chargebee Checkout API to collect the remaining information (Specifically payment details for example). Chargebee will take care of the PCI Compliance, all that James has to do is fill in this questionnaire.
Benefits of using API integration:
Checkout via API would require developer efforts from your end. Please refer to this documentation to learn more.
Chargebee's In-app Checkout supports 3DS payments. All you need to do is complete our SCA checklist, and Chargebee will start handling 3DS payments via In-app Checkout.
For scenarios which do not involve immediate payment like Update Payment Method, Subscription with trial etc., Chargebee performs minimum amount 3DS authorization. This ensures that subsequent payments can mostly go through without customer intervention. The authorized amount will be voided automatically.
For scenarios which involve immediate payment as in Subscription without trial, Upgrade Subscription etc., Chargebee takes care of initiating the 3DS flow and allowing 3DS verification to happen.