PTKDMobile App Security
Knowledge base / PTKD-REVIEW-EXTERNAL-PAYMENTS
medium M8 MASVS-CODE-1 static analysis PTKD-REVIEW-EXTERNAL-PAYMENTS

Payment SDK without in-app purchase (3.1.1 risk)

A third-party payment SDK (Stripe, PayPal, Braintree, Razorpay) is in the build and the app has no store billing (StoreKit / Google Play Billing). That is fine for physical goods and real-world services, but selling digital content or features this way is rejected (App Store 3.1.1; Google Play Payments policy).

How it's exploited

A payment SDK like Stripe or PayPal is in the build and the app has no StoreKit or Play Billing. Selling digital content, subscriptions or features that way is rejected (App Store Guideline 3.1.1, Google Play Payments policy). Physical goods and real-world services may use these SDKs.

Why it matters

Rejection, or removal after release if digital goods are sold outside store billing.

How to fix it

  1. List what the app sells. Digital goods and subscriptions move to StoreKit / Play Billing.
  2. Keep the payment SDK only for physical goods or services used outside the app, and say so in the review notes.

References