The SDK reports operational diagnostics to Finix through Datadog dd-sdk-ios 3.6.1 so Finix can monitor SDK health and support your integration:
- Diagnostic logs at informational level and above: SDK lifecycle events, transaction outcomes, and errors. Verbose debug logs stay on-device in the Xcode console.
- Log metadata: SDK version,
MerchantID, app bundle ID, API username, and environment. - Crash reports for crashes involving the SDK (unless disabled, see below).
The SDK never logs or transmits card numbers, CVVs, API passwords, or authentication tokens as log content.
Card reads happen entirely inside Apple's Tap to Pay on iPhone technology. The card number is encrypted by Apple on-device and is never visible to your app or to SDK code. The SDK transmits the encrypted payment payload to Finix over TLS with system certificate validation (App Transport Security). Results expose only masked card details (brand, last four).
TapToPayConfiguration(..., crashReportingEnabled: false)If your app ships its own crash reporter, disable SDK crash reporting, since two crash reporters in the same process can conflict. If your app initializes Datadog itself before creating the SDK, the SDK uses your instance without changing its configuration and does not enable crash reporting.
The XCFramework includes a PrivacyInfo.xcprivacy privacy manifest, which Xcode aggregates into your app's privacy report:
| Manifest entry | Value |
|---|---|
Tracking (NSPrivacyTracking) | false. No tracking, no tracking domains. |
| Collected data types | Crash Data, Performance Data, Other Diagnostic Data. |
| Collection attributes | Linked to identity (via merchant ID / username); not used for tracking; purpose: App Functionality. |
| Accessed API categories | UserDefaults (CA92.1). The SDK caches its own state. |
When you fill out App Store Connect's privacy questions, account for these SDK disclosures alongside your app's own.
Next: Prepare for App Review.