Offering Apple Pay in Your App

At a glance

Project structure

Source bundle/
├── Shared/
│   ├── PaymentHandler.swift
│   └── Configuration.swift
├── Offering-Apple-Pay-in-Your-App/
│   ├── AppDelegate.swift
│   ├── SceneDelegate.swift
│   ├── ViewController.swift
│   ├── Base.lproj/
│   │   └── LaunchScreen.storyboard
│   └── Info.plist
├── Watch App Extension/
│   ├── ExtensionDelegate.swift
│   └── InterfaceController.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── Offering-Apple-Pay-in-Your-App.xcodeproj/
    ├── .xcodesamplecode.plist
    └── project.pbxproj

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 11 project/configuration file(s) and 9 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["InterfaceController"]
    N3["PaymentHandler"]
    N4["PassKit APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

Offering-Apple-Pay-in-Your-App/AppDelegate.swift:10 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into PassKit (Apple Pay and Wallet).

Ownership and state

classDiagram
    PaymentHandler o-- PKPaymentAuthorizationController : paymentController
    PaymentHandler o-- PaymentCompletionHandler : completionHandler
    PaymentHandler *-- Array : supportedNetworks
    PaymentHandler *-- PKPaymentAuthorizationStatus : paymentStatus

Ownership evidence

Shared/PaymentHandler.swift:15 — stored dependency or nearest verified ownership anchor

class PaymentHandler: NSObject {
    // ...
    var paymentController: PKPaymentAuthorizationController?
    // ...
}

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Class and protocol design

Offering-Apple-Pay-in-Your-App/AppDelegate.swift:11 — representative type boundary

class AppDelegate: UIResponder, UIApplicationDelegate {
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

Offering-Apple-Pay-in-Your-App/AppDelegate.swift:11 — representative boundary

class AppDelegate: UIResponder, UIApplicationDelegate {
}

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Naming conventions

• Types: Controller: InterfaceController, ViewController; Delegate: AppDelegate, ExtensionDelegate, SceneDelegate; Handler: PaymentHandler.
• Protocols: no local protocol declaration in the scanned source.
• Methods: applePayStatus, shippingMethodCalculator, startPayment, paymentAuthorizationController, paymentAuthorizationControllerDidFinish, applyDiscount, viewDidLoad, payPressed.
• Files: Shared/PaymentHandler.swift, Offering-Apple-Pay-in-Your-App/AppDelegate.swift, Shared/Configuration.swift, Offering-Apple-Pay-in-Your-App/SceneDelegate.swift, Offering-Apple-Pay-in-Your-App/ViewController.swift, Watch App Extension/ExtensionDelegate.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches UIKit, PassKit, WatchKit, MapKit through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation