Asynchronous Methods
Stay organized with collections
Save and categorize content based on your preferences.
Asynchronous Methods
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-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."],[[["\u003cp\u003eSome Card API methods are asynchronous to accommodate Payment Integrators who need a specific processing sequence.\u003c/p\u003e\n"],["\u003cp\u003eThe Card API uses a single version for each method, prioritizing asynchronous processing for simplicity.\u003c/p\u003e\n"],["\u003cp\u003ePayment Integrators needing synchronous processing can implement a workaround by delaying acknowledgment until after calling the \u003ccode\u003efooResultNotification\u003c/code\u003e endpoint.\u003c/p\u003e\n"]]],["The Card API utilizes asynchronous methods to accommodate Payment Integrators that need specific processing sequences. To simplify development and maintenance, only asynchronous versions are supported, rather than both asynchronous and synchronous options. Payment Integrators requiring synchronous processing can implement a workaround by delaying the return of the \"ACKNOWLEDGED\" status until they have successfully completed the `fooResultNotification` endpoint call. This allows for synchronous processing within an asynchronous framework.\n"],null,["Asynchronous Methods\n\n\nSeveral 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\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.\n\n\u003cbr /\u003e"]]