Geodesic Solutions Community Wiki

User Tools

Site Tools

You are here: Auction and Classified Software Support Home » Developers » geoClasses Tips » geoTransaction
developers:geoclass:geotransaction:start

Differences

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

Link to this comparison view

Next revision 		Previous revision
developers:geoclass:geotransaction:start [2009/06/09 19:27]
jonyo created 		developers:geoclass:geotransaction:start [2014/09/25 16:55] (current)
Line 17: Line 17:
  
 ===== setGatewayTransaction($custom_id) ===== ===== setGatewayTransaction($custom_id) =====
-Can be used by gateways, to have an easily search able field((Since the field in the DB is a varchar, looking up a transaction by this field should be fast, by using geoTransaction::getTransaction($gateway_transaction_id).)) that goes with the transaction id that the gateway expects.+Can be used by gateways, to have an easily search able field((Since the field in the DB is a varchar, looking up a transaction by this field should be fast, by using geoTransaction::getTransaction($gateway_transaction_id).)) that goes with an external transaction id used in the external payment gateway's system, to link up the Geo transaction with the ID provided by the gateway.
  
 ==== Common Pitfalls: ==== ==== Common Pitfalls: ====
  
-**Max length is 255**:  If a gateway needs a longer ID length, store the first 255 chars using setGatewayTransaction() for faster and easier "lookup" of the transaction.  But then store the full ID in the transaction's registry.  See the code snipped further below for an example of how to code for it.+**Max length is 255**:  If a gateway needs a longer ID length, store the first 255 chars using setGatewayTransaction() for faster and easier "lookup" of the transaction.  But then store the full ID in the transaction's registry.  See the code snippet further below for an example of how to code for it.
  
 **ID Cannot be numeric**:  If the ID passed into geoTransaction::getTransaction($id) is numeric, it only looks up transactions with that ID as the internal ID.  So if the "gateway transaction ID" is numeric, the transaction will not be found when you try to use geoTransaction::getTransaction($id), unless you add a string to it to ensure it is not numeric.  See the code snippet below for an example of how to code for this: **ID Cannot be numeric**:  If the ID passed into geoTransaction::getTransaction($id) is numeric, it only looks up transactions with that ID as the internal ID.  So if the "gateway transaction ID" is numeric, the transaction will not be found when you try to use geoTransaction::getTransaction($id), unless you add a string to it to ensure it is not numeric.  See the code snippet below for an example of how to code for this:
developers/geoclass/geotransaction/start.1244575632.txt.gz · Last modified: 2014/09/25 16:55 (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
CC Attribution-Noncommercial-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki