Skip to main content
net10.0-ios26.0

.NET bindings for the StripePaymentSheet Swift library

Published
Jun 1, 2026
4mo ago
Total Downloads
1.4K
1,351

Install

dotnet add package SwiftBindings.Stripe.PaymentSheet --version 25.16.0
ProductVersions
.NET
net10.0-ios26.0

README

SwiftBindings.Stripe.PaymentSheet

Native Swift interop bindings for StripePaymentSheet — Stripe's drop-in payment UI for the iOS SDK. Renders all enabled payment methods, handles 3D Secure, Apple Pay, and saved-card flows, and returns a result your app can act on. Pair with CustomerSheet to manage saved payment methods. 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#.

Installation

dotnet add package SwiftBindings.Stripe.PaymentSheet

Requirements

  • .NET 10.0+
  • iOS 15.0+
  • macOS host for development

Usage

Customise appearance

using StripePaymentSheet;

var appearance = PaymentSheet.Appearance.Default;
appearance.CornerRadius = 12.0;
appearance.BorderWidth = 2.0;

Configure and present

// Construct PaymentSheet with a PaymentIntent client secret produced by your backend.
// var sheet = new PaymentSheet(paymentIntentClientSecret, configuration);
// sheet.Present(from: viewController, completion: result => { ... });

Address collection

var addressType = new AddressViewController.AddressDetails.AddressType(
    city: "San Francisco",
    country: "US",
    line1: "123 Market St",
    line2: null,
    postalCode: "94107",
    state: "CA");
var details = new AddressViewController.AddressDetails(addressType, name: "Test User");

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.

Changes from Previous Version

No structural changes between v25.15.0 and v25.16.0.

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.