Web checkout for iOS and Android apps with Stripe

Open Web in the dashboard and work through the checklist. You need a Stripe account and a RevenueDot project with your app.

1. 01

   Connect Stripe

   Add a web provider and pick Stripe, then save a restricted API key from your Stripe Dashboard. Add the RevenueDot webhook endpoint in Stripe and select checkout.session.completed.

2. 02

   Add a web config

   Set the app name, logo, theme colors, Terms and Privacy links, support email, your app's URL scheme and what happens after payment.

3. 03

   Create web products

   RevenueDot creates a Stripe Product and a Price in your account and a RevenueDot product whose store identifier is the Stripe price id. You can also use a price you already have.

4. 04

   Put web products in an offering

   A package can hold your App Store product, your Google Play product and your web product. The web pages show the packages that have a web product.

5. 05

   Share a link or publish a funnel

   Send buyers to a purchase link or a funnel. They pay on Stripe Checkout and get a redemption link on the success page and by email.

Each purchase arrives as INITIAL_PURCHASE (TRIAL during a trial) or NON_RENEWING_PURCHASE with store: STRIPE. Renewals, cancellations and refunds follow from Stripe's webhooks.

• The buyer opens a purchase link or funnel and picks a plan.
• RevenueDot creates a Stripe Checkout Session with your key and sends the buyer to Stripe's payment page.
• Stripe returns the buyer to the success page. RevenueDot reads the session from Stripe and records the purchase once, whichever of the success page or the webhook arrives first.
• The buyer opens the redemption link, the app calls redeemWebPurchase, and the entitlement is active.
• If the page already knows the app user id (?app_user_id= or the iOS SDK's web checkout), the purchase goes straight to that user and no redemption is needed.

Billing periods are P1W, P1M, P3M, P6M and P1Y. trial_days adds a free trial to each checkout. type is subscription, consumable or non_consumable.

curl -s -X POST "$REVENUEDOT_URL/v2/projects/$PROJECT_ID/apps/$APP_ID/web_products" \
  -H "Authorization: Bearer $SECRET_KEY" -H "Content-Type: application/json" \
  -d '{"display_name":"Pro monthly","type":"subscription","price":{"amount":9.99,"currency":"USD"},"duration":"P1M","trial_days":7,"entitlement_ids":["entl1a2b3c4d5e"]}'

Create a restricted key in your Stripe Dashboard and leave everything else at None. Web billing needs write access because RevenueDot creates products, prices, Checkout Sessions, coupons and promotion codes for you.

Check the App Store and Google Play rules for linking to external purchases in each country before you send buyers from inside an app to web checkout.

• Pages use your logo, app name and colors, with your Terms, Privacy and support links.
• The success page shows Open the app and the App Store and Google Play buttons. With success_mode: redirect, RevenueDot sends the buyer to your own page with the redemption link in the query.
• Buyers can use a discount code or get an automatic discount. See web discounts in the docs.
• Pages live at /pay/<project>/<page> on the API host, or on a custom domain you verify with a CNAME and a TXT record.
• Use a test-mode Stripe key first. Purchases are then sandbox data, kept out of production charts.

• Connect with Stripe (OAuth). Until then you paste a restricted key.
• Paddle as a web provider.
• An embedded checkout, such as Stripe Elements on your own page, and the purchases-js in-SDK Web Billing checkout. RevenueDot's checkout is a hosted page.
• Apple Pay domain registration for a custom domain.