Heads up: this post contains affiliate links. If you click through and complete a qualifying purchase, trial, or signup, we may earn a commission or fixed bounty at no cost to you. We verify factual claims against current sources and clearly note when guidance is documentation-based rather than personal use. Full disclosure →

Apple Card has been the trickiest connection in personal finance apps since launch. Most aggregators (Plaid, Finicity, MX) can’t connect to Apple Card directly because Apple’s banking partner (Goldman Sachs, transitioning to Chase) doesn’t expose a standard connection API. So how do you get Apple Card transactions into Monarch?

Monarch supports Apple Card via a special iPhone-based export flow — different from a normal bank link, but it works. Here’s the verified walkthrough including Apple Cash and Apple Savings.

The short version: Apple Card connects via the iPhone Wallet app's monthly statement export, NOT via Plaid/Finicity/MX. You'll export a CSV from your iPhone, then upload to Monarch. This works for Apple Card, Apple Cash, and Apple Savings. Sign up for Monarch's free trial with code SMARTMONEY for 50% off year one.

Why Apple Card is different

Most aggregators connect to banks via Plaid, Finicity, or MX. These services have direct API agreements with banks (Chase, Wells Fargo, Bank of America, etc.) that allow read-only access to transaction data. Monarch's standard account connection UI — Apple Card uses a different (manual export) flow

Apple Card runs on a different model. The card is issued by Goldman Sachs (transitioning to Chase in 2025-2026 per public reports) but doesn’t expose a public banking API. Apple’s stance has historically been that Apple Card data lives in your Wallet app and isn’t available to third-party aggregators.

The result: Monarch (and every other budgeting app) can’t auto-sync Apple Card via Plaid. Instead, Monarch supports Apple Card through a manual export workflow that uses a feature Apple does provide: monthly statement exports from the Wallet app.

What you can sync from the Apple ecosystem

Monarch supports three Apple-issued accounts via this workflow:

  • Apple Card — the credit card
  • Apple Cash — the prepaid card / Apple Pay balance
  • Apple Savings — the high-yield savings account paired with Apple Card

For all three, the connection method is the same: monthly export from your iPhone, upload to Monarch.

Step-by-step: connecting Apple Card

Per Monarch’s Help Center documentation:

Step 1: Export your Apple Card statement from iPhone

  1. Open the Wallet app on your iPhone (the Apple Wallet, not a third-party app)
  2. Tap Apple Card
  3. Tap Card Balance
  4. Tap the statement period you want to export (the most recent closed statement)
  5. Scroll to the bottom and tap Download PDF Statement OR Export Transactions (varies by iOS version)
  6. Choose CSV as the export format
  7. Tap the Share icon
  8. Save the CSV to Files (or AirDrop to your computer)

The CSV contains all transactions from that statement period — date, merchant, amount, category (Apple’s auto-categorization).

Step 2: Get the CSV onto your computer

Apple Card export is iPhone-only. To upload to Monarch (which is web-based for imports), you need to get the CSV from your phone to a computer.

Three options:

Option A — AirDrop:

  1. After export, tap Share → AirDrop
  2. AirDrop to your Mac
  3. CSV appears in your Downloads folder

Option B — Files app + iCloud Drive:

  1. After export, save to Files → iCloud Drive
  2. On your computer, open iCloud.com or the Files app on Mac
  3. Download the CSV from iCloud Drive

Option C — Email it to yourself:

  1. After export, tap Share → Mail
  2. Email the CSV to yourself
  3. Open email on computer, download attachment

Step 3: Upload the CSV to Monarch

  1. Sign in to Monarch on web (app.monarchmoney.com)
  2. Go to Accounts in the left navigation
  3. Click + Add Account
  4. Click Upload CSV at the bottom of the modal
  5. Select the Apple Card CSV
  6. Map columns: Date, Description (Merchant), Amount, Category
  7. Choose the destination account in Monarch:
    • If first-time Apple Card import, create a new manual account named “Apple Card” with type “Credit Card”
    • If you’ve imported before, select the existing Apple Card manual account
  8. Confirm and import

Monarch processes the import. Apple Card transactions appear in your Cash Flow, Budget, and other views.

Step 4: Repeat monthly

Apple Card statements close monthly. Each month, repeat steps 1-3 with the new statement. Monarch will deduplicate transactions if there’s overlap (e.g., your prior statement ended Feb 28, your new statement starts Feb 28).

For ongoing maintenance:

  • Set a calendar reminder for the day after your Apple Card statement closes (typically end of month)
  • Spend 5 minutes doing the export-and-upload
  • Your Monarch data stays current within ~30 days

Apple Cash and Apple Savings

The same workflow applies to Apple Cash and Apple Savings. From your iPhone Wallet:

  • Apple Cash: Wallet → Apple Cash → tap balance → Statements → export CSV
  • Apple Savings: Wallet → Apple Savings → Statements → export CSV

Each is a separate manual account in Monarch. Treat them as you would separate bank accounts.

Tip — set up a recurring monthly task. Monarch's [Recurring view](/blog/how-to-track-subscriptions-monarch/) won't help here (it tracks transactions, not workflows), but a calendar reminder works. Most users handle Apple Card export on the 1st of each month with their other monthly money tasks. Try Monarch's free trial with code SMARTMONEY for 50% off year one.

Why doesn’t Apple Card connect like other cards?

Three reasons, in increasing order of importance:

1. Apple’s design philosophy. Apple positions Apple Card as a privacy-first product where your transaction data lives on your iPhone, not in third-party aggregators. The lack of API access is intentional, not a technical oversight.

2. Goldman Sachs’ (and now Chase’s) banking infrastructure. Apple Card is issued by Goldman, transitioning to Chase. Neither has prioritized exposing Apple Card transactions through Plaid / Finicity / MX. The card system uses different infrastructure than Goldman’s other products.

3. Compliance and consent. Even if Apple wanted to, exposing Apple Card transactions to third-party aggregators would require a new consent flow from each user. Apple has historically been resistant to “data flows out of Apple’s ecosystem” patterns for privacy reasons.

The export-CSV workflow is Apple’s compromise: you can get your data, but it requires explicit user action each month rather than continuous API access.

What this means for budgeting

The monthly-export pattern has tradeoffs:

Pros:

  • Apple Card data does eventually appear in Monarch
  • You retain control over what gets shared (you choose to export)
  • Privacy-preserving by design

Cons:

  • Manual workflow each month (vs always-current other accounts)
  • Up to 30 days lag between transactions and Monarch visibility
  • Risk of forgetting to export, leaving Apple Card data missing

For users who heavily use Apple Card, the manual workflow is a real friction. Some users handle this by:

  1. Limiting Apple Card to specific use cases — e.g., only Apple ecosystem purchases (Apple Music, App Store, Apple Hardware) where you don’t need real-time tracking
  2. Using a non-Apple Card primary — and treating Apple Card as a secondary card for cash-back optimization on certain merchants
  3. Doing exports weekly instead of monthly — Apple Card lets you export current statement data even before close (though deduplication on import becomes more important)

If Apple Card real-time visibility is critical to you, you may end up frustrated with any budgeting app — this is a fundamental Apple limitation, not a Monarch issue.

Monarch alternatives for Apple Card users

If the manual workflow is a deal-breaker:

  • Use a different primary card. Many users keep Apple Card for Apple-ecosystem purchases only and use a different card (Chase Sapphire, Amex, Capital One, etc.) for everything else. The non-Apple card connects normally via Plaid.
  • Use Apple’s own budgeting features. Apple Card has built-in spending insights in the Wallet app. Less powerful than Monarch but always-current.
  • Don’t budget at the card level. Track total spending by category in Monarch, ignore which card was used. Less granular but simpler.

Some users decide Apple Card just isn’t worth the friction with budgeting apps and migrate primary spending to a different card. Up to you whether the cash-back / privacy benefits of Apple Card outweigh the budgeting friction.

Common questions

Will Apple ever support direct API access?

Possibly. The transition from Goldman Sachs to Chase (announced for 2025-2026) might bring Chase’s standard API access patterns. As of May 2026, the manual export flow is still the only option. Watch for Monarch’s Help Center updates.

What about Apple Card Family?

Apple Card Family (multiple users on one Apple Card) exports per-user transactions if each family member does their own export. The primary cardholder can also export the full family transaction history.

Can Monarch’s mobile app handle Apple Card upload?

No — CSV upload is web-only. You’ll export from iPhone, transfer to a computer (AirDrop or iCloud), and upload via web at app.monarchmoney.com.

What about Apple Pay (without Apple Card)?

Apple Pay isn’t a card — it’s a payment method that uses your existing cards. If you use Apple Pay with your Chase / Bank of America / etc. card, those transactions sync normally via Plaid.

Will my Apple Card transactions auto-categorize correctly in Monarch?

Apple Card’s CSV includes an Apple-side category. When you import, you can map Apple’s categories to Monarch’s categories. Monarch’s auto-categorization will then learn from your manual mappings over time.

What about Apple Savings interest?

Apple Savings interest payments show up in the monthly statement export. Categorize them as “Interest Income” when uploading to Monarch.

Does the manual export include pending transactions?

No — Apple Card’s CSV only includes posted transactions from a closed statement. Pending transactions are visible in Wallet but don’t export.

What if I forget to export for 2-3 months?

You can still export historical statements from Wallet and import each month’s CSV separately. Monarch deduplicates if you accidentally re-import the same period.

Is the manual workflow secure?

Yes — the CSV is yours to handle as you choose. Apple’s export, your transfer, your upload. Monarch doesn’t see any credentials or have any direct access to Apple’s systems.

Can I use a script to automate this?

Some users have built personal automation (Shortcuts on iPhone + iCloud Drive + Mac scripts that auto-import). Open-source community projects exist. Officially, Monarch doesn’t support automated Apple Card imports — it’s manual by design.

What about Citi, Chase Sapphire, and other premium cards?

Those connect normally via Plaid / Finicity / MX. No special workflow required. Apple Card is the unusual case in the personal-finance landscape.

Get Apple Card data into Monarch
7-day free trial gives you full access including manual CSV import. Use code SMARTMONEY at checkout to drop your first year to $49.99 (50% off, covers both partners). The Apple Card workflow is monthly but everything else syncs automatically.
Start a 7-Day Free Trial →

Code SMARTMONEY · WSJ Best Overall Budgeting App · 4.9 stars across 60,000+ reviews

For users who heavily use Apple Card and want simpler tracking, Apple’s built-in Wallet insights are always-current but limited. For users with a mix of Apple Card + other cards, Monarch handles the rest of your accounts seamlessly while Apple Card requires the manual monthly workflow.

Related reading:

Not financial, legal, or tax advice. We earn a commission if you sign up for Monarch through a link on this page; the price is the same. Apple Card connection workflow verified against Monarch’s Help Center documentation as of May 7, 2026. Apple’s data export options and Monarch’s import flow can change — check current documentation if anything in this guide doesn’t match your experience.