Async Funds Transfer Flow
Stay organized with collections
Save and categorize content based on your preferences.
Asynchronous Funds Transfer Flow
Overview
The asynchronous funds transfer flow is used to handle user-initiated payments where the Payment Integrator challenges the user prior to capturing funds.
How the flow works
The diagram below shows a user-initiated purchase.
Purchase flow-User present
The objects in the diagram include the following:
- User: This is the person who wants to purchase something through Google.
- Google UI/Device: The interface, where the customer begins to make a purchase.
- Google Server: The backend server at Google that sends the asynchronous capture command to the Payment Integrator Server.
- Payment Integrator: The backend server of the integrator that acknowledges the asynchronous capture command, challenges the user directly, and responds to Google with the capture result.
In this purchase flow, the user is in session. They begin the flow by starting to purchase an item.
- The User begins to purchase an item through the Google UI.
- The purchase information is sent to the Google Server.
- Google’s Server sends the
AsynchronousCapture request (GPT, amount) to the Payment Integrator.
- The Payment Integrator sends back an Acknowledge response to the Google Server.
- The Payment Integrator sends a USSD challenge to the User's Device.
- The User completes the challenge and the Device sends the Challenge Response.
- The Payment Integrator sends the
CaptureResultNotification
- The Google Server responds with Success to the Payment Integrator.
- The Google Server sends back a Success response to the Google UI.
- The items are delivered to the customer.
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-10-16 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-16 UTC."],[[["The asynchronous funds transfer flow is designed for user-initiated payments where the Payment Integrator challenges the user before capturing funds."],["This flow involves a multi-step process where the user initiates a purchase through Google UI, Google server sends a request to the Payment Integrator, and the Payment Integrator challenges the user directly for authorization."],["After the user completes the challenge, the Payment Integrator notifies Google Server about the capture result, leading to successful payment and delivery of items."],["Key players in this flow include the user, Google UI/Device, Google Server, and the Payment Integrator, each with specific roles in facilitating secure transactions."]]],["The asynchronous funds transfer flow involves a user purchasing an item via Google. The Google Server sends an `AsynchronousCapture` request to the Payment Integrator, which then acknowledges the request and challenges the user via USSD. After the user completes the challenge, the Payment Integrator sends a `CaptureResultNotification` to the Google Server. The Google server then responds with success and the items are delivered.\n"]]