Stay organized with collections
Save and categorize content based on your preferences.
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.
[[["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-09-03 UTC."],[[["\u003cp\u003eSome Card API methods are asynchronous to accommodate Payment Integrators who need sequential processing.\u003c/p\u003e\n"],["\u003cp\u003eGoogle provides only asynchronous versions of these methods for simplicity and easier maintenance.\u003c/p\u003e\n"],["\u003cp\u003ePayment Integrators requiring synchronous processing can achieve it by delaying the ACKNOWLEDGED response until after successfully calling the \u003ccode\u003efooResultNotification\u003c/code\u003e endpoint.\u003c/p\u003e\n"]]],["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"],null,["Several methods in the Card API are asynchronous only. These methods are\nasynchronous when Google anticipates some Payment Integrators will\nrequire the following sequence (e.g. due to batch files).\n\nWhat if a Payment Integrator requires synchronous processing?\n=============================================================\n\nRather than support asynchronous and synchronous versions of each method, Google\nhas opted to only support one version per method. This is intended to make the\nlaunch of new Payment Integrators and ongoing maintenance simpler.\n\nIf a Payment Integrator only supports synchronous processing, they can implement\nthe following sequence. Specifically, they can wait to return ACKNOWLEDGED until\nafter that have successfully called the fooResultNotification endpoint."]]