Insights

Why Purser reads your Apple Card through Wallet and never asks for a login

Apple Card is not a normal bank account, so Purser cannot reach it the way it reaches other cards. Here is how the iPhone reads it through FinanceKit, what the server receives, and what happens when you say no.

Every other card in Purser comes in through the same door. You connect your bank to SimpleFIN Bridge, and Purser’s server reads the balances and transactions from there. It is read-only. Purser never sees your bank password.

Apple Card does not use that door. It is not something you can connect through a bank aggregator. For Purser that was a real problem, because it was the one card we wanted most to include.

This post is about how we solved it, and what the solution does and does not do.

The card lives in Wallet, so the phone has to read it

Apple gives apps one supported way to read Apple Card: a framework called FinanceKit. It reads the card from Wallet, on the iPhone, after you give permission.

That shapes everything. FinanceKit runs on iPhone only. It does not run on iPad. It does not run in the Simulator. And it does not cover Apple Cash or Apple Savings, only the card.

So the arrangement is the reverse of the other feeds. For a bank, the server reads and the app displays. For Apple Card, the phone reads, and the phone sends what it read to the server. The iPad and the other person’s devices then show what the phone posted.

There is no password in this at all. Purser never asks you for an Apple Card login, because there is nothing to hand over. The only thing you do is tap Allow on Apple’s own permission screen.

One file touches FinanceKit

We keep the framework at arm’s length. A single file in the app, FinanceKitSource.swift, is the only one that imports FinanceKit. Everything it returns is the app’s own plain types: an account with a name, an amount owed, an available amount and a limit, and a transaction with a date, an amount, a payee and a status.

The rest of the app, and every test, only ever sees those plain types. This was a testing decision as much as a design one. FinanceKit does not run in the Simulator, so a test that needed the real framework could not run on a build machine at all. Because the source sits behind a small interface, the tests use a fake one. Real behaviour still needs a test on a real iPhone, and we say so in the docs instead of pretending the fake covers it.

The same file asks Apple for history in batches, using a token that remembers where the last read stopped. It reads what changed since then and ends. It does not leave a listener running in the background.

What the server receives

The phone posts the card as plain numbers and rows to one route on the server. The route turns that into the same account and transaction records that every other feed writes. A few rules keep that safe.

Ids are hashes. The account and every transaction get an id made from a hash of FinanceKit’s own id. The id is stable, so sending the same rows again rewrites them in place and never adds a second copy. And it cannot be reversed back to Apple’s id.

Spend is negative. The phone sends purchases as negative amounts, money in as positive, and the amount owed as a positive balance. That is how every card is stored in Purser, so the rest of the maths does not need a special case.

A limit on size. One post can carry at most a thousand transactions, and each id and payee has a length cap. Anything past that is refused instead of half-saved.

Nothing sensitive in the log. When the server refuses an upload, it now says which check failed: no id, no amount or no date. The log line carries fixed text only, never an amount, a payee or an id. We added this after a refusal on a phone said only that Purser could not take the upload, and nothing anywhere recorded why.

Not doubling your history

You may already have typed in an Apple Card balance by hand, or imported a statement file, before the live feed arrives. Two rules stop the first live sync from doubling that history.

First, the manual Apple Card is adopted, not replaced. It keeps its id, so the typed balances and imported statements stay on the same account. From then on it stops being a place you can import a file into. A live feed and a file import do not both write to one account.

Second, if a row from FinanceKit matches a row you already imported from a statement file, with the same amount and the same payee within three days, the server skips it.

When you say no, or cannot say yes

The feature is offered only on iPhone, only in a real household, and never in the demo household used for App Review. Everywhere else, Apple Card stays a manual account.

That covers four cases. An iPad. A permission you denied. A phone with no Apple Card. And a review session. In all of them you can still type in the balance and limit yourself, or share a screenshot of the balance to Purser. The screenshot is read on the device by Apple’s Vision framework, which means the image does not need to leave the phone to be understood.

We also added a guard during review. A demo session on a phone that had once connected Wallet could, in principle, have read the real card and tried to post it under the demo sign-in. The server would have refused it with a 403. But the card should not leave the phone at all, so the app now checks on both paths, at sign-in and in the foreground, and never syncs in a review session.

Taking it back

You can withdraw the permission at any time in Settings on the iPhone. Purser then stops receiving the card.

Deleting your account removes your Apple Card account and its transactions from the service. In the first version of deletion, that was not true. Deletion removed accounts you typed in by hand, but a FinanceKit account was a different source, and it stayed behind. We caught it and fixed it, and the next post in this series, what happens when you delete your Purser account, tells that story.

If you want the Apple Card data gone without deleting your account, write to the support address on the Trust page.

What it cost us to get here

FinanceKit needs an entitlement that Apple grants on application. It is not on by default, and it takes time.

We applied on 25 September. Apple first closed the request because FinanceKit was not offered in our region. Once we confirmed the app would be distributed in the US only, Apple granted the entitlement on 5 October, ten days after we applied.

Until it arrived, Apple Card had to be a manual account. In the meantime the manual route was good enough to keep the card total and the credit page honest. The feature sits behind a single switch in the project settings, so it can be hidden again if we ever need to.

The short version

Apple Card cannot be reached by a bank link, so the phone reads it. The phone reads it through one file, posts plain rows, and the server stores them under hashed ids so nothing is doubled. You can say no and keep using Purser. You can take it back. Purser asks for no login because there is no login to ask for.

Drafted with AI assistance.