How do I validate an Apple IAP receipt locally using TPInAppReceipt?

Import the library and use `AppReceipt.local` or `AppReceipt.receipt(from: data)` to decode, then call `validate()` for default checks. The README provides code examples for decoding and validation steps.

TPInAppReceipt vs RevenueCat: which is better for In-App Purchases?

TPInAppReceipt is a lightweight, local validation library for Swift apps, while RevenueCat is a full-featured SaaS with server-side management and cross-platform support. Choose TPInAppReceipt for simple, on-device validation; RevenueCat for comprehensive backend services.

Does TPInAppReceipt support async/await?

Yes, it supports async/await with methods like `AppReceipt.local`, but also offers a blocking API via `@_spi(Blocking)` for synchronous contexts, as mentioned in the README under 'Blocking Mode'.

How to check if a subscription is active with TPInAppReceipt?

After decoding the receipt, use the `receipt.purchases` property to query purchases and check their status, such as expiration dates or introductory offer eligibility, as detailed in the subscription management features.

Is TPInAppReceipt secure enough for App Store submission?

Yes, it performs local validation with certificate and signature checks, aligning with Apple's guidelines. However, for highest security, Apple recommends server-side validation in some cases, so assess your app's specific needs.

How to migrate from TPInAppReceipt v3 to v4?

Refer to the migration guide linked in the README, which covers breaking changes and updates. Key steps include adapting to new APIs and ensuring compatibility with Swift 6.0+ and Xcode 16+.

Open-Awesome

TPInAppReceipt

MITSwift4.0.2

A pure-Swift library for reading and validating Apple In-App Purchase receipts locally on iOS, macOS, tvOS, watchOS, and visionOS.

GitHub

713 stars94 forks0 contributors

What is TPInAppReceipt?

TPInAppReceipt is a Swift library for reading and validating Apple In-App Purchase receipts locally on Apple platforms. It solves the problem of verifying purchase authenticity and subscription status without relying on server-side validation, making it ideal for apps that handle IAPs directly on the device.

Target Audience

iOS, macOS, tvOS, watchOS, and visionOS developers who implement In-App Purchases and need to validate receipts locally for security, subscription management, or offline functionality.

Value Proposition

Developers choose TPInAppReceipt for its pure-Swift implementation, type-safe API, and comprehensive local validation features, which simplify receipt handling while maintaining security and performance without external dependencies.

Overview

Reading and Validating In App Purchase Receipt Locally.

Use Cases

Best For

Validating In-App Purchase receipts locally without server calls
Checking subscription status and introductory offer eligibility
Implementing secure receipt parsing in Swift-based Apple apps
Handling IAP validation in offline-capable applications
Migrating from server-side receipt validation to on-device verification
Building apps that require fast, reliable receipt decoding and integrity checks

Not Ideal For

Apps requiring server-side receipt validation for compliance with high-security standards or centralized logging
Cross-platform projects using frameworks like Flutter or React Native, as it's Swift-only
Developers needing to validate receipts from non-Apple payment systems or platforms
Teams still using Xcode versions below 16, due to its Swift 6.0+ requirement

Pros & Cons

Pros

Pure-Swift Implementation

The library is written entirely in Swift with no external dependencies, ensuring seamless integration and leveraging modern Swift features for type safety and performance.

Comprehensive Local Validation

It performs default validation including certificate chain, signature, hash, and metadata checks, as per the README, providing robust security without server calls.

Flexible Subscription Management

Enables querying purchases, checking subscription status, and verifying introductory offer eligibility, essential for handling In-App Purchases effectively.

Custom Validator Support

Supports advanced use cases via @VerifierBuilder for custom validation logic, giving developers fine-grained control over validation rules.

Blocking API for Sync

Offers a synchronous API for contexts where async/await is not available, ensuring compatibility with legacy or specific coding environments.

Cons

Apple Platform Exclusivity

Only supports iOS, macOS, tvOS, watchOS, and visionOS, making it unsuitable for cross-platform or non-Apple projects, limiting its versatility.

Breaking Changes in Updates

The README includes a migration guide for v4.0, indicating that updates can introduce breaking changes that require significant code adjustments and maintenance effort.

Limited to Local Validation

While it validates locally, it doesn't integrate with Apple's server validation for real-time checks, which might be a security gap for apps needing highest assurance.

Dependency on Latest Swift

Requires Swift 6.0+ and Xcode 16+, which could be a barrier for teams on older toolchains or projects with legacy codebases.

Frequently Asked Questions

Related Projects

SwiftyStoreKit

Lightweight In App Purchases Swift framework for iOS 8.0+, tvOS 9.0+ and macOS 10.10+ ⛺

Stars6,678

Forks805

Last commit1 year ago

RMStore

A lightweight iOS library for In-App Purchases

Stars2,411

Forks446

Last commit6 years ago

card.io-iOS-SDK

card.io provides fast, easy credit card scanning in mobile apps

Stars2,294

Forks548

Last commit8 years ago

CreditCardForm-iOS

CreditCardForm is iOS framework that allows developers to create the UI which replicates an actual Credit Card.

Stars1,467

Forks166