Handling Payment Requests with SiriKit

At a glance

Project structure

Source bundle/
├── Payments/
│   ├── AppDelegate.swift
│   └── PaymentHistoryViewController.swift
├── PaymentsFramework/
│   ├── PaymentProvider.swift
│   ├── Contact.swift
│   ├── ContactLookup.swift
│   ├── Payment.swift
│   └── PaymentsFramework.h
├── PaymentsIntentsExtension/
│   ├── SendPaymentIntentHandler.swift
│   ├── IntentsExtension.swift
│   └── INPerson+Contact.swift
├── Configuration/
│   └── SampleCode.xcconfig
└── Payments.xcodeproj/
    └── .xcodesamplecode.plist

Structure observations

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

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["PaymentHistoryViewController"]
    N3["PaymentProvider"]
    N4["Intents APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

Payments/AppDelegate.swift:12 — 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 Intents.

Ownership and state

classDiagram
    AppDelegate o-- UIWindow : window
    PaymentHistoryViewController *-- PaymentProvider : paymentProvider
    PaymentHistoryViewController o-- Any : activeAppNotificationObserver
    PaymentHistoryViewController o-- NumberFormatter : amountFormatter

Ownership evidence

Payments/AppDelegate.swift:15 — stored dependency or nearest verified ownership anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    // ...
    var window: UIWindow?
    // ...
}

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

Payments/AppDelegate.swift:13 — 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

Payments/PaymentHistoryViewController.swift:13 — representative boundary

class PaymentHistoryViewController: UITableViewController {
    // ...
    private let paymentProvider = PaymentProvider()
    // ...
}

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: PaymentHistoryViewController; Delegate: AppDelegate; Handler: SendPaymentIntentHandler; Provider: PaymentProvider.
• Protocols: no local protocol declaration in the scanned source.
• Methods: applicationDidFinishLaunching, loadPaymentHistory, viewDidLoad, tableView, canSend, send, validate, save.
• Files: Payments/AppDelegate.swift, Payments/PaymentHistoryViewController.swift, PaymentsFramework/PaymentProvider.swift, PaymentsIntentsExtension/SendPaymentIntentHandler.swift, PaymentsFramework/Contact.swift, PaymentsFramework/ContactLookup.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches Intents, PaymentsFramework, UIKit 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