skills/mobile-payment-integration-specialist/SKILL.md
Mobile payment integration for Stripe, Apple Pay, Google Pay, in-app purchases, and subscription management. Activate on: mobile payments, Stripe SDK, Apple Pay, Google Pay, in-app purchase, StoreKit 2, Google Play Billing, subscription management, payment sheet. NOT for: backend payment processing (use api-architect), general e-commerce (use frontend-architect), financial compliance (use security-auditor).
npx skillsauth add curiositech/windags-skills mobile-payment-integration-specialistInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Expert in integrating mobile payments including Stripe, Apple Pay, Google Pay, in-app purchases, and subscription lifecycle management.
Activate on: "mobile payments", "Stripe SDK mobile", "Apple Pay integration", "Google Pay", "in-app purchase", "StoreKit 2", "Google Play Billing", "subscription management", "payment sheet", "RevenueCat"
NOT for: Backend payment processing → api-architect | General e-commerce → frontend-architect | Financial compliance → security-auditor
| Domain | Technologies | |--------|-------------| | Direct Payments | Stripe Mobile SDK 23.x, Payment Sheet, Braintree | | iOS IAP | StoreKit 2, App Store Server API, Server Notifications V2 | | Android IAP | Google Play Billing 7.x, BillingClient, PurchaseFlow | | Subscriptions | RevenueCat, Superwall, Qonversion, custom server logic | | Express Pay | Apple Pay, Google Pay, Link (Stripe) |
What are you selling?
│
├─ Digital content consumed IN the app (stickers, coins, premium features)
│ └─ MUST use In-App Purchases (Apple/Google mandatory)
│ ├─ Apple: StoreKit 2 + App Store Server API
│ └─ Android: Google Play Billing Library
│
├─ Physical goods or real-world services (food, rides, consulting)
│ └─ CAN use direct payment (Stripe, Braintree)
│ └─ No 30% commission
│
└─ Reader/media apps (Netflix, Kindle, Spotify)
└─ CAN link to web for signup (US/EU/KR as of 2026)
└─ External purchase entitlement via App Store Server API
import { useStripe } from '@stripe/stripe-react-native';
function CheckoutScreen({ amount }: { amount: number }) {
const { initPaymentSheet, presentPaymentSheet } = useStripe();
async function checkout() {
// 1. Create PaymentIntent on your server
const { clientSecret, ephemeralKey, customerId } = await api.post(
'/create-payment-intent',
{ amount, currency: 'usd' }
);
// 2. Initialize Payment Sheet
const { error: initError } = await initPaymentSheet({
merchantDisplayName: 'My Store',
paymentIntentClientSecret: clientSecret,
customerEphemeralKeySecret: ephemeralKey,
customerId,
applePay: { merchantCountryCode: 'US' },
googlePay: { merchantCountryCode: 'US', testEnv: __DEV__ },
defaultBillingDetails: { name: 'Jane Doe' },
});
if (initError) return handleError(initError);
// 3. Present Payment Sheet
const { error: payError } = await presentPaymentSheet();
if (payError) {
if (payError.code === 'Canceled') return; // User dismissed
handleError(payError);
} else {
// Payment succeeded — server confirms via webhook
navigation.navigate('OrderConfirmation');
}
}
return <Button onPress={checkout} title={`Pay $${amount}`} />;
}
// Modern StoreKit 2 (async/await)
import StoreKit
class SubscriptionManager {
func purchase(_ product: Product) async throws -> Transaction {
let result = try await product.purchase()
switch result {
case .success(let verification):
let transaction = try checkVerified(verification)
await transaction.finish()
// Notify server of purchase for server-side validation
await api.verifyPurchase(transactionId: transaction.id)
return transaction
case .pending:
throw SubscriptionError.pendingApproval // Ask-to-Buy
case .userCancelled:
throw SubscriptionError.cancelled
@unknown default:
throw SubscriptionError.unknown
}
}
// Listen for subscription status changes
func observeTransactionUpdates() async {
for await result in Transaction.updates {
guard let transaction = try? checkVerified(result) else { continue }
await handleTransactionUpdate(transaction)
await transaction.finish()
}
}
}
[ ] Server-side payment verification via webhooks (never trust client)
[ ] Correct payment model chosen (IAP for digital, Stripe for physical)
[ ] Apple Pay and Google Pay configured as express checkout options
[ ] Subscription lifecycle handled: trial, renewal, cancellation, grace period
[ ] Pending transactions (Ask-to-Buy) handled gracefully
[ ] Product IDs fetched from store at runtime (not hardcoded)
[ ] Restore purchases implemented for app reinstalls
[ ] Receipt validation on server (App Store Server API / Google Developers API)
[ ] Refund handling via server notifications
[ ] Price displayed in user's local currency
[ ] Subscription management screen links to platform settings
[ ] PCI DSS compliance: no raw card data touches your servers (use Stripe tokenization)
tools
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book.
testing
Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — `Cache-Control` directives per RFC 9111, `stale-while-revalidate` and `stale-if-error` per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs.
development
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
tools
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.