We are observing unexpected behavior in Apple Wallet for transactions processed via an online delivery platform. Here is the specific flow:
Initial Authorization: The original order was placed for $22.30.
Order Amendment: The user added an item 10 minutes later for $6.20, bringing the total to $28.50.
The Issue: Apple Wallet only displays the $6.20 transaction. The initial $22.30 amount is not visible in the transaction list.
Technical Verification:
We confirmed that both backend authorization messages for the original amount and the add-on were approved.
We verified that the final settlement amounts correctly reflect the sum of both charges ($28.50).
We have confirmed the transaction lifecycle completed successfully on our end.
Despite this, the customer only sees the $6.20 entry in their Wallet history, which creates confusion as it doesn't reflect the total spent.
Has anyone encountered this sync issue between settlement totals and Wallet display, or is there a specific way we should be linking these related authorizations? Thanks!
Hi @Simon_gft,
You wrote:
[...] Has anyone encountered this sync issue between settlement totals and Wallet display, or is there a specific way we should be linking these related authorizations? [...]
The most likely root cause of this issue that the $6.20 was submitted as a new independent authorization rather than a properly linked incremental authorization.
Transactions in Wallet are driven by the payment issuer/network notification tied to the original Apple Pay transactionIdentifier in the payment token. When the amendment is submitted without linking fields, the network treats it as a separate, unrelated auth—which is exactly the broken transaction display you have reported.
The three most common scenarios that result in only the $6.20 being visible:
- Two independent auths with separate cryptograms: Two separate entries, or only the latest visible.
- Amendment submitted without the original network transaction ID: Network overwrites/suppresses the original with the new auth.
- Original auto-revered by issuer when second auth arrived: Only $6.20 services as an active auth.
For achieve the expected behavior, it must be understood that the Apple Pay cryptogram from PKPaymentToken or ApplePayPaymentToken is single-use and one-per-order. All subsequent amount changes must be handled as incremental authorizations at the network level, using no new Apple Pay cryptogram at all.
In your specific use case, since the final order amount is unknown at checkout time, use PKPaymentSummaryItem or ApplePayLineItem with the .pending type to set the correct customer expectation upfront:
let request = PKPaymentRequest()
request.paymentSummaryItems = [
PKPaymentSummaryItem(
label: "Estimated Total",
amount: NSDecimalNumber(string: "22.30"),
type: .pending // <- signals that the amount may change
)
]
This tells the customer the amount shown in an estimate before any incremental auth is needed, which is the recommended pattern for delivery use cases.
Cheers,
Paris X Pinkney | WWDR | DTS Engineer
