Skip to main content
net10.0-ios26.2net10.0-maccatalyst26.2

Native Swift interop bindings for Apple ProximityReader

Published
May 19, 2026
5mo ago
Total Downloads
1.5K
1,547

Install

dotnet add package SwiftBindings.Apple.ProximityReader --version 26.2.3
ProductVersions
.NET
net10.0-ios26.2net10.0-maccatalyst26.2

README

SwiftBindings.Apple.ProximityReader

Native .NET bindings for Apple's ProximityReader framework — Tap to Pay on iPhone, contactless payment-card reads, and mobile-document NFC reads. 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.Apple.ProximityReader

Requirements

  • .NET 10.0+
  • iOS 26.2+, Mac Catalyst 26.2+
  • macOS host for development
  • iPhone XS or later
  • Tap to Pay on iPhone entitlement (Apple-issued)

Usage

using Foundation;
using ProximityReader;

// A purchase for $1.99 USD
var amount = NSDecimalNumber.FromString("1.99");
var transaction = new PaymentCardTransactionRequest(
    amount,
    currencyCode: "USD",
    type: PaymentCardTransactionRequest.TransactionType.Purchase);

// A non-payment card verification (e.g. age verification)
var verify = new PaymentCardVerificationRequest(currencyCode: "USD");

// A VAS request (Apple Wallet pass / loyalty)
var vas = new VASRequest();

The PaymentCardReader, MobileDocumentReader, StoreAndForwardBatch, and supporting result/error types are all bound. See Tap to Pay on iPhone for end-to-end onboarding (entitlement request, merchant attestation, session lifecycle).

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. ProximityReader is part of the Apple SDK; refer to Apple's licensing for the underlying framework.

Changes from Previous Version

No structural changes between v26.2.1 and v26.2.3.

Adoption Assessment

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

Compatibility metadata lists 2 target frameworks; confirm the exact target used by your application.

Related Guides & Workflows

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