developer:soap:methods:runtransactionapi

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
developer:soap:methods:runtransactionapi [2009/01/13 14:18]
hmcgowan
developer:soap:methods:runtransactionapi [2009/07/02 10:22]
epouchak
Line 1: Line 1:
 +<embed ..:​contents/>​
 +
 ====== runTransactionAPI ====== ====== runTransactionAPI ======
  
Line 6: Line 8:
  
  
-The parameters argument is an array containing any of the variable names supported by the [[developer:transactionapi|Transaction API]]. ​+The parameters argument is an array containing any of the variable names supported by the [[transactionapi|Transaction API]]. ​
  
-This method requires more work to implement than the [[developer:​soap:​methods:​runtransaction|runTransaction]] method, and typically should not be your first choice for processing transactions. The one benefit of using this method is that it provides a direct interface to the transaction processing engine of the gateway. As new fields are added to the system they can be used immediately via this method without having to wait for the next Soap release or generate a new WSDL link. The [[developer:​soap:​methods:​runtransaction|runTransaction]] method on the other hand has its [[developer:​soap:​objects:​transactionrequestobject|TransactionRequestObject]] tied to the Soap release (and wsdl url). To access new fields you would have to generate a new WSDL link.+This method requires more work to implement than the [[runtransaction|runTransaction]] method, and typically should not be your first choice for processing transactions. The one benefit of using this method is that it provides a direct interface to the transaction processing engine of the gateway. As new fields are added to the system they can be used immediately via this method without having to wait for the next Soap release or generate a new WSDL link. The [[runtransaction|runTransaction]] method on the other hand has its [[developer:​soap:​objects:​transactionrequestobject|TransactionRequestObject]] tied to the Soap release (and wsdl url). To access new fields you would have to generate a new WSDL link.
  
 //NOTE:// In previous releases this method was called runOldApi. //NOTE:// In previous releases this method was called runOldApi.
Line 18: Line 20:
 ===== Syntax ===== ===== Syntax =====
  
-[[developer:​soap:​objects:​TransactionResponse]] **runTransactionAPI** ( [[developer:​soap:​objects:​ueSecurityToken]] Token, [[developer:​soap:​objects:​FieldValue]] Parameters )+[[..:​objects:​TransactionResponse]] **runTransactionAPI** ( [[developer:​soap:​objects:​ueSecurityToken]] Token, [[..:​objects:​FieldValue]] Parameters )
  
  
Line 26: Line 28:
  
 ^Type   ​^Name ​  ​^Description ​  ^ ^Type   ​^Name ​  ​^Description ​  ^
-|[[developer:​soap:​objects:​ueSecurityToken]] |Token |Merchant security token: used to identify merchant and validate transaction.| +|[[..:​objects:​ueSecurityToken]] |Token |Merchant security token: used to identify merchant and validate transaction.| 
-|[[developer:​soap:​objects:​FieldValue]] ​ |Parameters |List of variables to pass to Transaction API.|+|[[..:​objects:​FieldValue]] ​ |Parameters |List of variables to pass to Transaction API.|
  
  
Line 39: Line 41:
 ==== PHP ==== ==== PHP ====
  
-For directions on how to set up the WSDL link, create "​$token"​ and "​$client,"​ see the [[developer:​soap:​howto:​php|PHP SOAP How-to]].+For directions on how to set up the WSDL link, create "​$token"​ and "​$client,"​ see the [[..:​howto:​php|PHP SOAP How-to]].
  
  
developer/soap/methods/runtransactionapi.txt · Last modified: 2010/04/07 10:40 by charlie

Page Tools