Apple Card Bill Split Feature in iOS 27 Explained: Who Can Use It

iOS 27 will push receipt-scanning, itemized bill splitting directly into Apple Wallet and Messages, turning Apple Cash into the settlement layer for group dining tabs. Announced at WWDC 2026 last month, the Apple Card bill split feature in iOS 27 lets whoever paid the full check photograph the receipt, assign individual line items to specific people, and send Apple Cash reimbursement requests without leaving apps already on their phone. The wider iOS 27 release is expected this September.

A quick framing note: the feature is tied to Apple Cash and Apple Wallet, not Apple Card specifically. Apple Card is what draws many readers to this story; the actual workflow has nothing to do with which card covered the tab.

How it works: scan receipt, assign items, request payment

The person who paid photographs the receipt. A live camera scan works, and so does an existing photo taken earlier, according to Apple. Apple Intelligence reads the line items. The payer then taps individual items to assign each one to a specific person in the group. Wallet or Messages generates Apple Cash payment requests based on those assignments.

That item-by-item assignment is the part that matters. Splitting the total evenly is fast and consistently wrong. It ignores the person who ordered the side salad while everyone else ordered steak, the couple who shared an appetizer, the friend who skipped dessert. Assigning the pasta to one person and the ribeye to another is how people actually want to settle up, and Apple is embedding that logic natively inside Wallet and Messages rather than routing users to a third-party app to do the same work, as MacRumors reported ahead of the WWDC announcement.

The feature surfaces in three places: Messages, Apple Wallet, and through Visual Intelligence via the iPhone camera, Apple confirmed. Those are all applications that are typically already open in the minutes after a meal.

The photo option deserves attention as a separate point. Supporting an existing image means the workflow isn't limited to the restaurant table. Someone who paid the tab and forgot to split it can handle it an hour later, from home, using a photo already in their camera roll. That detail is quietly useful for the person who always ends up chasing reimbursements the next morning.

What Apple has and hasn't confirmed

Apple confirmed receipt scanning, per-item assignment, and Apple Cash requests through Wallet and Messages. The mechanics beyond that are undocumented.

How the feature handles tax and tip is unclear. Whether a shared appetizer can be split fractionally across multiple people, or assigned as a flat amount to each, Apple hasn't said. How it processes discounts, comps, or service charges is unknown. And receipt-scanning accuracy on real-world restaurant tickets, thermal paper with faded ink, abbreviated item names, handwritten bills from smaller restaurants, remains publicly untested.

These aren't minor edge cases. A group dinner tab that includes a shared starter, a split entree, a service charge, and a discount code covers all of them simultaneously. The workflow Apple has described handles a clean, well-printed receipt with unambiguous line items. Whether it holds up in messier conditions is a question that gets answered in September when users can test it in the field.

Apple Pay's checkout flow is also getting an updated design in iOS 27, giving users more context when choosing payment methods, Apple said. That's part of the same broader effort to make Wallet a more complete financial layer, not just a tap-to-pay shortcut.

How to split bills with Apple Wallet in iOS 27: who can actually use it

The reimbursement mechanism is Apple Cash, full stop. Every person receiving a payment request needs an iPhone with Apple Cash active, per Apple's announcement. The person who paid the original tab can use any payment method to cover it, but collecting back from the group runs through Apple Cash.

That creates a concrete constraint. One Android user at the table, or one iPhone user who never set up Apple Cash, falls outside the workflow entirely. Apple has not disclosed whether those individuals receive a request through any alternative channel, or whether the payer has to chase their share through a separate method. The feature is frictionless for groups that are uniformly on iPhone with Apple Cash active. For groups that aren't, the payer still ends up handling at least one share the old way.

The geographic picture is similarly bounded. Apple Cash is available only in the United States, and because the bill-splitting workflow ties directly to it, the feature is likely U.S.-only at launch, MacRumors noted, given Apple Cash's current availability. Apple has not issued explicit guidance on international access.

iOS 27 is currently in public beta. The wide release is expected in September.

Why this matters beyond the dinner table

Credit card products have always been built around the purchase moment: rewards, APRs, fraud protection, checkout UX. What happens after one person covers a group bill has been quietly delegated to third-party apps. Venmo, Splitwise, a group text full of payment handles and half-remembered amounts. No major card issuer has treated post-payment reimbursement as a product problem it owns.

Apple's approach is structurally different from those third-party tools. Venmo and Splitwise require every participant to download an app and maintain an active account. The friction of getting six people to use the same platform has always been the practical ceiling on how useful those tools are at the actual table. Apple's version starts with the iPhone camera and ends in Wallet or Messages applications that are already installed, already signed in, already open.

The entry point is the camera. The exit point is a Messages thread the group is probably already in. That's a meaningfully shorter path than "download this app, create an account, connect your bank, find everyone else in the app." Whether that shorter path translates to better adoption is an open question, but the structural advantage is real.

The harder engineering question is whether receipt-scanning accuracy holds at scale on real-world tabs. A well-formatted printed receipt from a corporate chain is a different problem than a handwritten ticket from a neighborhood spot with abbreviated item names. That gets tested in September. The more durable strategic question is whether banks and card issuers start treating post-payment coordination as something they should own, or keep outsourcing it to Venmo and Splitwise while Apple builds the case that a payments platform should handle the full event, not just the transaction moment. So far, no major issuer has moved in that direction. Apple's announcement is the clearest argument yet that someone should.

The constraints are real, but so is the upgrade

For U.S. iPhone users in groups already operating inside Apple's ecosystem, this is a genuinely useful addition. Itemized splitting is meaningfully better than dividing the total by headcount. The ability to use an existing photo rather than scanning on the spot makes the workflow practical for more situations than a live-at-the-table-only tool would be.

The ceiling is equally real. Apple Cash is the only payment rail for the collect-back mechanism. A single non-participant, one Android user, one person who never enabled Apple Cash, breaks the automated workflow for their portion of the tab. International users are likely excluded at launch, based on Apple Cash's current U.S.-only status, though Apple has not confirmed that explicitly.

What Apple hasn't done yet is solve the mixed-ecosystem problem. That's the harder version of this feature, and it's the one that would make it genuinely universal rather than useful-within-constraints. For now, the bill-splitting feature in iOS 27 is the best native solution Apple has built for post-payment coordination, and the first time a major platform has treated that coordination as something it owns. Both things can be true at once.