Several methods in the Card API are asynchronous only. These methods are
asynchronous when Google anticipates some Payment Integrators will
require the following sequence (e.g. due to batch files).
What if a Payment Integrator requires synchronous processing?
Rather than support asynchronous and synchronous versions of each method, Google
has opted to only support one version per method. This is intended to make the
launch of new Payment Integrators and ongoing maintenance simpler.
If a Payment Integrator only supports synchronous processing, they can implement
the following sequence. Specifically, they can wait to return ACKNOWLEDGED until
after that have successfully called the fooResultNotification endpoint.
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-09-03 UTC.
[null,null,["Last updated 2024-09-03 UTC."],[[["Some Card API methods are asynchronous to accommodate Payment Integrators who need sequential processing."],["Google provides only asynchronous versions of these methods for simplicity and easier maintenance."],["Payment Integrators requiring synchronous processing can achieve it by delaying the ACKNOWLEDGED response until after successfully calling the `fooResultNotification` endpoint."]]],["The Card API utilizes asynchronous-only methods to accommodate Payment Integrators that require specific processing sequences. Google chose this approach over supporting both synchronous and asynchronous methods to simplify implementation and maintenance. Integrators needing synchronous processing can achieve it by waiting to acknowledge a request as \"ACKNOWLEDGED\" until after they've successfully completed their processing, including calling a specific result notification endpoint.\n"]]