Confirmed users
1,158
edits
Marketplace/TransactionNumbers: Difference between revisions
Jump to navigation
Jump to search
Marketplace/TransactionNumbers (view source)
Revision as of 21:13, 3 September 2013
, 3 September 2013→Payment Server (solitude)
| Line 40: | Line 40: | ||
| '''id''' || The internal primary key on the table | | '''id''' || The internal primary key on the table | ||
|- | |- | ||
| '''uuid''' || An internal uuid generated when you start the transaction. When the transaction is completed in solitude we send a post back to the marketplace. The Marketplace stores it in tracking_id on the contribution. So zamboni.tracking_id equals solitude.uuid. | | '''uuid''' || An internal uuid generated when you start the transaction. When the transaction is completed in solitude we send a post back to the marketplace. The Marketplace stores it in tracking_id on the contribution. So zamboni.tracking_id equals solitude.uuid. This is also the external tracking id that we send to the provider. | ||
|- | |- | ||
| '''uid_pay''' || An id from the provider that relates to the authorization of transaction. In Bango, this is the result of billingConfigurationId. In Paypal, it is the paykey. | | '''uid_pay''' || An id from the provider that relates to the authorization of transaction. In Bango, this is the result of billingConfigurationId. In Paypal, it is the paykey. | ||