Skip to main content

.NET bindings for the StripeApplePay Swift library

Total Downloads
1.3K
1,346
Published
Sep 22, 2026
26d ago

Get Started

dotnet add package SwiftBindings.Stripe.ApplePay --version 26.11.0
ProductVersions
.NET
net10.0-ios26.0

README

SwiftBindings.Stripe.ApplePay

Native Swift interop bindings for StripeApplePay β€” the lightweight Apple Pay integration module of the Stripe iOS SDK. Lets you offer Apple Pay without pulling in the heavier StripePaymentSheet / StripePayments modules. These are not Objective-C proxy wrappers β€” they use .NET 10's native Swift interop for direct, high-performance calls into Swift APIs from C#.

πŸ“– Full usage guide β†’ β€” Apple Pay via PaymentSheet, PKPaymentRequest construction, and why the standalone STPApplePayContext delegate isn't callable from C#.

Installation

dotnet add package SwiftBindings.Stripe.ApplePay

You'll typically also need SwiftBindings.Stripe.Core for the API client.

Requirements

  • .NET 10.0+
  • iOS 15.0+
  • macOS host for development
  • Apple Pay capability enabled on the app, Merchant ID configured in App Store Connect

Usage

using StripeApplePay;
using StripeCore;

// Configure once with your publishable key
var client = new STPAPIClient("pk_test_...");

// Present Apple Pay via STPApplePayContext (delegate-driven flow):
//   1. Build a PKPaymentRequest
//   2. Construct STPApplePayContext with the request and a delegate
//   3. Present from your view controller

Documentation

How It Works

These bindings are auto-generated by Swift Dotnet Bindings using .NET 10's native Swift interop via the SwiftBindings SDK.

License

The bindings are MIT licensed. The Stripe iOS SDK is MIT licensed β€” see Stripe's license.

Downloads by Version

Similar & Alternative Packages

Hand-picked matching NuGet libraries based on tags & ecosystem

Depended On By

Find packages that declare this package as a dependency. NuGet does not provide a reverse-dependency endpoint, so candidates are checked on demand.

Adoption Assessment

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

Compatibility metadata lists 1 target framework; confirm the exact target used by your application.

Related Guides & Workflows

Learn how to evaluate, integrate, or audit this package in your .NET project.