TAMITOS Move development: when an in-app gift can show a thank-you

TAMITOS Move's November 10 mobile change adds a path for opening a family gift in Stripe's native PaymentSheet when the server offers it. The app then waits for its own server to report the recorded gift before showing a thank-you. The change is visible in the reviewed mobile implementation. Availability in a public app build depends on release and platform evidence.
What does the payment sheet handle?
A payment sheet gives the person a place to review and complete the payment. Before opening it, the reviewed TAMITOS Move code requests a quote and checks the amounts returned for the sheet against the intended gift and total. That check connects the amount the person selected to the next screen they see.
The app also distinguishes three outcomes from the sheet: completed, cancelled and failed. Those outcomes determine what the app does next. A completion result leads to a check for the recorded gift. A cancellation returns the person to the story. A presentation failure follows an error path. This keeps each next step tied to the result of the attempt.
When does hosted checkout open?
The implementation can use the existing hosted Stripe checkout when the app cannot prepare the in-app sheet or when the platform is configured to use hosted checkout. The boundary is whether an in-app sheet has already been presented. Once it has appeared, cancelling it or getting an error does not open a second payment page from the same action.
Imagine a person reviewing their gift on a phone and then closing the sheet to reconsider. If a browser checkout appeared immediately afterward, it would be hard to know whether closing the first screen had worked. In the reviewed flow, that action ends the presentation path. In a different case, where the phone is set to use hosted checkout from the beginning, the browser is the expected place to continue.
There is a practical review question here: can a person tell which screen owns their current action? Watch the transition from the story to payment, then back from payment to the story. Notice whether a cancellation leaves the person in a stable place where they can decide what to do next.
For a review, put the starting route and the outcome in the same note. For example, a test case can describe a native presentation that ends through cancellation and list the next screen the person should see. That makes the test about the person's experience, with the route selection and callback checks supporting it.
What makes the receipt a separate step?
The mobile implementation checks the server for the recorded gift after a completed sheet. The thank-you uses the amount from the server result. The payment interface and the receipt view therefore have separate responsibilities. The first tells the app that it can start looking for the receipt. The second has the record the app needs before displaying confirmation.
Stripe's mobile payments documentation explains the payment presentation flow and the role of server-side payment events. For related work in this product, see the TAMITOS Move gift status refresh article. That article focuses on the period after checkout when a receipt can still be pending.
What do the reviewed tests cover?
The repository includes widget tests that substitute a fake sheet presenter and a fake receipt check. One scenario supplies a completed presentation and a recorded result, then checks that the paid callback runs and that hosted checkout did not open. A cancellation scenario expects neither a receipt check nor a second payment page. Another case supplies a server response that disables the native route and expects the hosted route.
This test design lets a reviewer change a single condition without making a real payment. The cases document intended behavior around the app's presentation and confirmation. Device integration, actual server events and storefront availability each need their own evidence.
Why does this handoff matter?
The person should be able to distinguish the moment they finish with the sheet from the moment the app shows the recorded gift. Those moments can be close together, but their order matters when a receipt takes longer than expected. A review can recreate the delay and watch for a premature success message or a duplicate route back into checkout.
Direct gifts are separate from movement points and sponsored help. The TAMITOS Move points and sponsored help article explains that separate product flow. To follow other work on the app and its family tools, see the TAMITOS project at QORPO and the studio development feed.
QORPO