Skip to content
Keshav Raj
A phone completing an in-app purchase with a one-tap checkout glow and a coin dropping into a bag.
PAYMENTS STRIPIAP
SHIPPED iOS in-app purchase and the mobile fast checkout.I OWNED ImplementerOUTCOME IAP

IAP + mobile fast checkout

Keshav RajImplementer · 2021–23 · ShippedContact meResume PDF

Context

From 2021 to 2023 I worked on the payment side of the white-label learner app: iOS in-app purchase and the mobile fast checkout. Schools sell courses through many gateways and markets, and the store apps need in-app purchase compliance.

The problem

The store apps needed in-app purchase compliance, with prices shown in local terms. Separately, the mobile app needed a faster checkout.

What I did

  1. In December 2021 I rewrote the subscription scripts and added localised in-app purchase prices for iOS. I reworked that in May 2023.

  2. I extended subscription mode to all products in 2022.

  3. I built the mobile fast checkout, all 13 commits of it, with a matching change in the shared UI library, and made the phone number mandatory on the web fast checkout.

  4. I fixed a pricing-bundle bug during the Geo pay rollout and fixed build issues for the Easebuzz gateway.

Key decision

I acted as the integrator for teammates' gateway work and kept my own changes to the mobile in-app purchase and fast checkout code. The web fast checkout, split payment and the Easebuzz and Geo pay work were colleagues' work, and I credit them for it.

The trade-off was breadth against ownership: I did not rewrite gateways I had not built.

Result

Multi-gateway and in-app purchase checkout shipped across 2021 to 2023. I have no conversion figures, so I do not claim an effect on conversion.

What I learned

I would again keep payment changes small and owned, since many gateways touched one checkout. Next I would add conversion tracking before the change, so the effect can be measured.

Stack

  • React Native
  • Next.js
  • Apple in-app purchase
  • Razorpay
Play the world →